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

From Peter Eisentraut
Subject Re: Precedence of standard comparison operators
Date
Msg-id 54EF902E.8000606@gmx.net
Whole thread Raw
In response to Re: Precedence of standard comparison operators  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Precedence of standard comparison operators
List pgsql-hackers
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.




pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: json_populate_record issue - TupleDesc reference leak
Next
From: Andres Freund
Date:
Subject: Re: Precedence of standard comparison operators