On Tue, May 3, 2016 at 11:48 AM, Robert Haas <robertmh...@gmail.com> wrote:
> OK, I see now: the basic idea here is that we can't prune based on the > newer XID unless the page LSN is guaranteed to advance whenever data > is removed. Currently, we attempt to limit bloat in non-unlogged, > non-catalog tables. You're saying we can instead attempt to limit > bloat only in non-unlogged, non-catalog tables without hash indexes, > and that will fix this issue. Am I right? Right. I was wondering whether there might be other avenues to the same end, but that is the most obvious fix. I'm hesitant to raise the alternatives because people seem to have entered "panic mode", at which point alternatives always look scary. -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
