On Wed, Jun 8, 2016 at 8:21 AM, Alvaro Herrera <alvhe...@2ndquadrant.com> wrote: > Tom Lane wrote: >> Michael Paquier <michael.paqu...@gmail.com> writes: >> > On Tue, Jun 7, 2016 at 12:31 PM, Michael Paquier >> > <michael.paqu...@gmail.com> wrote: >> >> On Tue, Jun 7, 2016 at 12:28 AM, Alvaro Herrera >> >> <alvhe...@2ndquadrant.com> wrote: >> >>> Hmm, so we could solve the complaint by adding an ANALYZE. I'm open to >> >>> that; other opinions? >> >> >> We could just enforce work_mem to 64kB and then reset it. >> >> > Or just set up work_mem to a wanted value for the duration of the run >> > of psql_crosstab. Attached is my proposal. >> >> I liked the ANALYZE idea better; this seems pretty ad-hoc. > > Done that way.
OK, thanks for fixing the issue! -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
