| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | David Gould <daveg(at)sonic(dot)net>, Andres Freund <andres(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org, Anand Ranganathan <arangana(at)adobe(dot)com>, Alex Eulenberg <aeulenbe(at)adobe(dot)com>, Ashokraj M <ashokraj(at)adobe(dot)com>, Hari <hari(at)adobe(dot)com>, Elein Mustain <mustain(at)adobe(dot)com> |
| Subject: | Re: Re: bulk_multi_insert infinite loops with large rows and small fill factors |
| Date: | 2012-12-12 15:37:00 |
| Message-ID: | 8646.1355326620@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> writes:
> The bug's been fixed now, but note that huge tuples like this will
> always cause the table to be extended. Even if there are completely
> empty pages in the table, after a vacuum. Even a completely empty
> existing page is not considered spacious enough in this case, because
> it's still too small when you take fillfactor into account, so the
> insertion will always extend the table.
Seems like that's a bug in itself: there's no reason to reject an empty
existing page.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavan Deolasee | 2012-12-12 17:31:14 | Re: PageIsAllVisible()'s trustworthiness in Hot Standby |
| Previous Message | Fujii Masao | 2012-12-12 15:36:48 | Re: [BUG?] lag of minRecoveryPont in archive recovery |