| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Florian Pflug <fgp(at)phlo(dot)org> |
| Cc: | Jim Nasby <jim(at)nasby(dot)net>, Josh Berkus <josh(at)agliodbs(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Marko Tiikkaja <marko(at)joh(dot)to>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: plpgsql.consistent_into |
| Date: | 2014-01-14 00:57:04 |
| Message-ID: | 24488.1389661024@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Florian Pflug <fgp(at)phlo(dot)org> writes:
> On Jan14, 2014, at 01:20 , Jim Nasby <jim(at)nasby(dot)net> wrote:
>> And if we've always had it, why on earth didn't we make STRICT the default
>> behavior?
> Dunno, but AFAIK pl/pgsql mimics Oracle's PL/SQL, at least in some aspects,
> so maybe this is one of the areas where we just do what oracle does.
STRICT is a relatively recent addition (8.2, looks like). One of the
reasons it got in was that the author didn't have any grandiose ideas
about making it the new default. I think this patch would have a lot
better chance if it was just adding another keyword as an alternative
to STRICT, and not hoping to impose the author's opinions on the rest
of the world. Whatever your opinion of the default behavior, the
fact that it's been that way for upwards of fifteen years without any
mass protests should give you pause about changing it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian Pflug | 2014-01-14 01:00:15 | Re: [PATCH] Negative Transition Aggregate Functions (WIP) |
| Previous Message | Jim Nasby | 2014-01-14 00:55:41 | Re: [Lsf-pc] Linux kernel impact on PostgreSQL performance |