Re: Drop --disable-floatN-byval configure options?

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Drop --disable-floatN-byval configure options?
Date: 2018-02-22 13:20:51
Message-ID: 8a9c2387-bb12-6f2a-bcff-d5907f53e534@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2/21/18 12:17, Tom Lane wrote:
> I don't actually envision changing the C code much at all; we might want
> to resurrect the old code at some point. I just want to reduce the number
> of supported configurations.

Yeah, it can exist like EXEC_BACKEND, as a way to manually simulate a
different architecture for testing. But we don't need it as an option
exposed to users.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2018-02-22 13:22:48 Re: Online enabling of checksums
Previous Message Thomas Munro 2018-02-22 13:18:28 Re: [HACKERS] SERIALIZABLE with parallel query