| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Simon Riggs <simon(at)2ndQuadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Precedence of standard comparison operators |
| Date: | 2015-02-26 21:34:11 |
| Message-ID: | 858C6C8E-26AB-49B8-BCEA-9165EF43FA17@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On February 26, 2015 10:29:18 PM CET, Peter Eisentraut <peter_e(at)gmx(dot)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 bigger and had security implications. Also people didn't really switch because of it until the default changed. At the very least there should be an option to error out, not warn.
---
Please excuse brevity and formatting - I am writing this on my mobile phone.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-02-26 21:54:02 | Re: logical column ordering |
| Previous Message | Peter Eisentraut | 2015-02-26 21:29:18 | Re: Precedence of standard comparison operators |