Re: Re: bulk_multi_insert infinite loops with large rows and small fill factors
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Heikki Linnakangas <hlinnakangas@vmware.com>
Cc: David Gould <daveg@sonic.net>, Andres Freund <andres@2ndquadrant.com>, pgsql-hackers@postgresql.org, Anand Ranganathan <arangana@adobe.com>, Alex Eulenberg <aeulenbe@adobe.com>, Ashokraj M <ashokraj@adobe.com>, Hari <hari@adobe.com>, Elein Mustain <mustain@adobe.com>
Date: 2012-12-12T15:37:00Z
Lists: pgsql-hackers
Heikki Linnakangas <hlinnakangas@vmware.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