On Thu, Mar 12, 2015 at 5:56 PM, Andres Freund <and...@2ndquadrant.com> wrote: > So, no hot standby enabled?
Right. > There've been some issues with seek(END) sometimes returning the wrong > length in the past. And I've seen a report that might indicate a similar > bug has been reintroduced. That could certainly cause such anerror. Perhaps. >> I am unfamiliar with this provisioning code, so, as I >> mentioned, offhand I cannot be entirely sure that there isn't some >> other code run when the problem originally arises (that I should have >> included in my report). > > It's probably worthwhile to dig out what's happening. I'll get to that after the backtrace. >> What I can tell you is that I saw the same error messages when I >> manually ran the statements generated by the above code within a >> transaction...until I ran "VACUUM FULL pg_auth_members;". > > You can reproduce that problem? How easily? If you can, please produce a > backtrace. It'll certainly be interesting to see whether that access is > through an index or whatnot. I suspect I can reproduce it quite easily. The next step should be to do a backtrace. I'll look at that tomorrow. -- Peter Geoghegan -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
