Skip site navigation (1) Skip section navigation (2)

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

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Brendan Jurd <direvus(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] Exorcise "zero-dimensional" arrays (Was: Re: Should array_length() Return NULL)
Date: 2013-03-25 17:14:15
Message-ID: 515085E7.9020208@agliodbs.com (view raw or flat)
Thread:
Lists: pgsql-hackers
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


In response to

Responses

pgsql-hackers by date

Next:From: Fujii MasaoDate: 2013-03-25 17:28:53
Subject: Re: odd behavior in materialized view
Previous:From: Atri SharmaDate: 2013-03-25 17:06:20
Subject: Re: Limiting setting of hint bits by read-only queries; vacuum_delay

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group