Robert Haas wrote:
I believe that user could get GIN's error about work_mem only intentionally:
- turn off autovacuum
Meanwhile, in the other thread, we're having a discussion about people
wanting to do exactly this on a database-wide basis during peak load
hours...
- decrease work_mem for at least ten times
- execute query
Why would the new work_mem need to be 10x smaller than the old work mem?
That is is way to get GIN's error emitted. Work_mem should be decreased
to catch a chance to get lossy tidbitmap.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
