From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Marina Polyakova <m(dot)polyakova(at)postgrespro(dot)ru> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Subject: | Re: master check fails on Windows Server 2008 |
Date: | 2018-02-20 18:23:26 |
Message-ID: | 11948.1519151006@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Marina Polyakova <m(dot)polyakova(at)postgrespro(dot)ru> writes:
> On 20-02-2018 3:37, Tom Lane wrote:
>> 4. Try to tweak the stats_ext.sql test conditions in some more refined
>> way to get the test to pass everywhere. This'd be a lot of work with
>> no guarantee of success, so I'm not too excited about it.
> Thank you for your explanations! I'll try to do something in this
> direction..
OK. The least painful fix might be to establish a different work_mem
setting just for that one query.
However, if you're intent on putting work into continued support of
--disable-float8-byval, I would *strongly* suggest setting up a buildfarm
member that runs that way, because otherwise we're pretty much guaranteed
to break it again. I continue to wonder if it's not better to just remove
the option and thereby simplify our lives. What's the actual value of
having it anymore?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2018-02-20 18:26:16 | Re: Option to ensure monotonic timestamps |
Previous Message | Andres Freund | 2018-02-20 18:20:23 | Re: ALTER TABLE ADD COLUMN fast default |