PG 9.0 and standard_conforming_strings
in [PgSql]
|
Prev: [HACKERS] PG 9.0 and standard_conforming_strings
Next: Package namespace and Safe init cleanup for plperl [PATCH]
From: Tom Lane on 29 Jan 2010 17:34 Josh Berkus <josh(a)agliodbs.com> writes: >> I stand by the position that it's way too late in the cycle for >> insufficiently-thought-out proposals for major behavioral changes. > I don't see how announcing this earlier in the dev cycle would help, at > all. We would have more than no-time-at-all to test it and fix any breakage. Just to start close to home, do you really trust either psql or pg_dump to be completely free of standard_conforming_strings issues? How about JDBC or ODBC? Python drivers? PLs? The really short and sweet answer is that if you have any ambition at all to ship 9.0 this year, it is too late to add new work items. This is a work item, and not a small one. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Tom Lane on 29 Jan 2010 17:44 Bruce Momjian <bruce(a)momjian.us> writes: > Well, since I asked in April of 2009, at the beginning of the cycle, 6 > years after the introduction of the variable, and we still are not doing > it, then let's stop pretending we will ever do it. We have made forward progress since that thread (we fixed the plpgsql parsing issues, partially in 8.4 and completely for 9.0). We can continue to make forward progress in the future. But *right now is not the time*. We have more than enough on our plates for 9.0 already, and just about nobody believes we are going to meet the schedule now. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Andres Freund on 29 Jan 2010 17:46 On Friday 29 January 2010 23:34:09 Tom Lane wrote: > Josh Berkus <josh(a)agliodbs.com> writes: > >> I stand by the position that it's way too late in the cycle for > >> insufficiently-thought-out proposals for major behavioral changes. > > > > I don't see how announcing this earlier in the dev cycle would help, at > > all. > The really short and sweet answer is that if you have any ambition at > all to ship 9.0 this year, it is too late to add new work items. This > is a work item, and not a small one. What about anouncing in the 9.0 releasenotes that it will be removed in 9.1? Andres -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Bruce Momjian on 29 Jan 2010 17:47 Andres Freund wrote: > On Friday 29 January 2010 23:34:09 Tom Lane wrote: > > Josh Berkus <josh(a)agliodbs.com> writes: > > >> I stand by the position that it's way too late in the cycle for > > >> insufficiently-thought-out proposals for major behavioral changes. > > > > > > I don't see how announcing this earlier in the dev cycle would help, at > > > all. > > The really short and sweet answer is that if you have any ambition at > > all to ship 9.0 this year, it is too late to add new work items. This > > is a work item, and not a small one. > What about anouncing in the 9.0 releasenotes that it will be removed in 9.1? You mean turned on by default, right? -- Bruce Momjian <bruce(a)momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Tom Lane on 29 Jan 2010 17:54
Andres Freund <andres(a)anarazel.de> writes: > What about anouncing in the 9.0 releasenotes that it will be removed in 9.1? That seems quite useless. I note that we've made such statements before and not followed through on them; one that just came up again is that contrib/xml2 is a couple releases past when it was said it'd be removed, and there is still no prospect of it really dying in the near future. The bottom line is that these sorts of changes take actual *work*, and not a trivial amount of it. No amount of blather in the documentation will substitute for somebody doing the work. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |