| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: installcheck failing on psql_crosstab |
| Date: | 2016-06-07 23:48:58 |
| Message-ID: | CAB7nPqTEwJ-Yq7gdv3PX6yB5iKDPYxF8ykxfcAE5_rf1Zsrfvw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 8, 2016 at 8:21 AM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> Tom Lane wrote:
>> Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
>> > On Tue, Jun 7, 2016 at 12:31 PM, Michael Paquier
>> > <michael(dot)paquier(at)gmail(dot)com> wrote:
>> >> On Tue, Jun 7, 2016 at 12:28 AM, Alvaro Herrera
>> >> <alvherre(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2016-06-08 00:25:13 | Re: [BUGS] Routine analyze of single column prevents standard autoanalyze from running at all |
| Previous Message | Alvaro Herrera | 2016-06-07 23:21:23 | Re: installcheck failing on psql_crosstab |