From: | Brendan Jurd <direvus(at)gmail(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH] Exorcise "zero-dimensional" arrays (Was: Re: Should array_length() Return NULL) |
Date: | 2013-03-25 05:47:28 |
Message-ID: | CADxJZo39GwAUOQBjRvtEYJew1j9wdju=r-C8w-i3uf7SbQFn1Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 25 March 2013 13:02, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> On 03/20/2013 04:45 PM, Brendan Jurd wrote:
>> Incompatibility:
>> This patch introduces an incompatible change in the behaviour of the
>> aforementioned array functions -- instead of returning NULL for empty
>> arrays they return meaningful values. Applications relying on the old
>> behaviour to test for emptiness may be disrupted. One can
>
> As a heavy user of arrays, I support this patch as being worth the
> breakage of backwards compatibility. However, that means it certainly
> will need to wait for 9.4 to provide adequate warning.
Thanks Josh, I appreciate the support.
>
> Brendan, how hard would it be to create a GUC for backwards-compatible
> behavior?
Good idea. I don't know how hard it would be (never messed with GUCs
before), but I'll take a swing at it and see how it works out.
Cheers,
BJ
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2013-03-25 08:11:14 | pgsql: Add PF_PRINTF_ATTRIBUTE to on_exit_msg_fmt. |
Previous Message | Simon Riggs | 2013-03-25 04:14:22 | Re: Request for vote to move forward with recovery.conf overhaul |