| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Alex Hunsaker <badalex(at)gmail(dot)com> |
| Cc: | Alexey Klyukin <alexk(at)commandprompt(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: arrays as pl/perl input arguments [PATCH] |
| Date: | 2011-01-12 19:27:05 |
| Message-ID: | 44CDF5D6-1E7C-4518-A69E-2C2A252DA2C2@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jan 12, 2011, at 11:22 AM, Alex Hunsaker wrote:
> Personally, I think the point of a compatibility GUC is that at some
> point in the distant future we can get rid of it. If we default to
> the old behavior thats going to be harder to do. +1 for defaulting to
> the new behavior.
+1
> [ Id actually vote for _not_ having a compatibility option at all, we
> change more major things than this IMHO every major release. (And even
> then some major things in minor releases, for example the removal of
> Safe.pm) ]
Yeah, but the removal of Safe.pm actually *improved* compatibility. This patch, without the GUC, would break it.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2011-01-12 19:27:09 | Re: pg_depend explained |
| Previous Message | Alex Hunsaker | 2011-01-12 19:22:55 | Re: arrays as pl/perl input arguments [PATCH] |