Re: Precedence of standard comparison operators - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Precedence of standard comparison operators
Date
Msg-id 858C6C8E-26AB-49B8-BCEA-9165EF43FA17@anarazel.de
Whole thread Raw
In response to Re: Precedence of standard comparison operators  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Precedence of standard comparison operators  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On February 26, 2015 10:29:18 PM CET, Peter Eisentraut <peter_e@gmx.net> wrote:
>On 2/25/15 5:15 PM, Simon Riggs wrote:
>> Having a warn_if_screwed parameter that we disable by default won't
>> help much because if you are affected you can't change that
>situation.
>> There are too many applications to test all of them and not all
>> applications can be edited, even if they were tested.
>
>My suggestion was to treat this like the standard_conforming_string
>change.  That is, warn for many years before changing.

I don't think scs is a good example to follow. For one it didn't work well. For another the impact of scs was imo
biggerand had security implications. Also people didn't really switch because of it until the default changed. At the
veryleast there should be an option to error out, not warn.
 



--- 
Please excuse brevity and formatting - I am writing this on my mobile phone.



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Precedence of standard comparison operators
Next
From: Alvaro Herrera
Date:
Subject: Re: logical column ordering