Postgres Pro
Downloads
Home   >   mailing lists

Re: [PATCH] Exorcise "zero-dimensional" arrays (Was: Re: Should array_length() Return NULL) - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: [PATCH] Exorcise "zero-dimensional" arrays (Was: Re: Should array_length() Return NULL)
Date
Msg-id 515085E7.9020208@agliodbs.com
Whole thread Raw
In response to Re: [PATCH] Exorcise "zero-dimensional" arrays (Was: Re: Should array_length() Return NULL)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCH] Exorcise "zero-dimensional" arrays (Was: Re: Should array_length() Return NULL)  (Greg Stark <stark@mit.edu>)
Re: [PATCH] Exorcise "zero-dimensional" arrays (Was: Re: Should array_length() Return NULL)  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Tree view 
Tom,

> No, it *isn't* a good idea.  GUCs that change application-visible
> semantics are dangerous.  We should have learned this lesson by now.

Really?  I thought that standard_conforming_strings was a great example
of how to ease our users into a backwards-compatibility break.   My
thought was that we change the behavior in 9.4, provide a
backwards-compatible GUC with warnings in the logs for two versions, and
then take the GUC away.

Whether that's worth the effort, though, is a question of how many
people are going to be affected by the compatibility break.  Maybe I can
do a survey.

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

pgsql-hackers by date:

Previous
From: Atri Sharma
Date:
Subject: Re: Limiting setting of hint bits by read-only queries; vacuum_delay
Next
From: Fujii Masao
Date:
Subject: Re: odd behavior in materialized view