2010/1/29 Tom Lane <t...@sss.pgh.pa.us>: > Josh Berkus <j...@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?
Do you mean that turning standard_conforming_string ON may lead to error with pg_dump, psql or something else ? (I don't care of projects outside the official postgresql tarball in this question) Whether the param is ON or OFF by default, what does that change in this area ? > > 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@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers > -- Cédric Villemain -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
