On 04/30/2015 12:09 PM, Alvaro Herrera wrote:
Joshua D. Drake wrote:
I take that back, it appears this table is heavily deleted from and also
uses the lo_manage() triggers.
Well, if it's heavily deleted, then it's probably also heavily vacuumed
and from time to time empty pages at the tail are removed by vacuum. It
might also be the case I was remembering, rather than regular TRUNCATE.
I don't think the vacuumlo stuff would have much to do with it issue; I
think it would only scan the table, then delete stuff from
pg_largeobject. It doesn't modify the table itself (unless I'm
misremembering)
Anyway, I don't remember that we reached any useful conclusion. Andres
suspected a PG bug, but we didn't find anything.
Well it certainly causes an outage unfortunately. Once the error occurs
postgresql will stop accepting requests (which is correct but still).
JD
--
Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Announcing "I'm offended" is basically telling the world you can't
control your own emotions, so everyone else should do it for you.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
