| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alex Hunsaker <badalex(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PG 9.0 and standard_conforming_strings |
| Date: | 2010-01-29 23:56:03 |
| Message-ID: | 4B637593.6060103@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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?
Oh, yeah. I was just thinking about the direct user and DBA issues; of
course if there's additional potential breakage, we'll have to defer it.
Too bad, it would have been a good time to break it from a user
perspective.
--Josh Berkus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-01-29 23:59:52 | Re: PG 9.0 and standard_conforming_strings |
| Previous Message | Andres Freund | 2010-01-29 23:15:08 | Re: PG 9.0 and standard_conforming_strings |