Re: pgsql: Change floating-point output format for improved performance.

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Change floating-point output format for improved performance.
Date: 2019-02-13 22:16:49
Message-ID: 87wom3mj2x.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

>>>>> "Andrew" == Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> writes:

>>> Cross-version upgrade is the big problem; I have no real idea how to
>>> make that test work short of adding another GUC; revert?

>> Andrew Dunstan might be able to help, although I'm not immediately
>> sure how...

Andrew> Me either. I can, of course, have the check module drop tables
Andrew> that make the tests fail, but that seems like bad course of
Andrew> action in this case. Meanwhile, I'm going to run a series of
Andrew> tests with different back branches to see the scope of the
Andrew> problem. Expect to see these in the buildfarm results today.

I think we know the scope of the problem - the test will fail if
upgrading any back branch to HEAD, since the pg_dump output is
different. But this discussion should probably continue on the Ryu
thread on -hackers rather than here.

--
Andrew (irc:RhodiumToad)

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2019-02-13 23:13:27 pgsql: Fix portability issues in pg_bitutils
Previous Message Andrew Dunstan 2019-02-13 20:47:47 Re: pgsql: Change floating-point output format for improved performance.