| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Joel Jacobson <joel(at)trustly(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Marko Tiikkaja <marko(at)joh(dot)to> |
| Subject: | Re: merging some features from plpgsql2 project |
| Date: | 2017-01-09 23:53:45 |
| Message-ID: | 3c311479-7059-f576-765f-e0d40f845549@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/9/17 5:12 PM, Merlin Moncure wrote:
> Agreed: If you want to break compatibility, pushing a new language is
> the better way than GUC. If you got consensus on this, having both
> languages side by side supported for a while (maybe 4-5 releases) is
> they way to go, and finally the only language is frozen and moved to
> extension. But this is a lot of work and aggravation, are you *sure*
> you can only get what you want with a full compatibility break?
FWIW, that work and aggravation part is what I hoped to avoid with GUCs.
I do think that whichever route we go, we're going to be stuck
supporting the old version for a LONG time. A big part of why
standard_conforming_strings was so ugly is users didn't have enough time
to adjust. If we'd had that enabled by default for 4-5 releases it
wouldn't have been nearly as much of an issue.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2017-01-09 23:56:48 | Re: merging some features from plpgsql2 project |
| Previous Message | Marko Tiikkaja | 2017-01-09 23:53:01 | Re: merging some features from plpgsql2 project |