Re: pg_dump and backslash escapes

Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > The basic issue is that we need to set standard_conforming_strings to
> > 'off' for loading into newer releases, >= 8.2, but that SET command is
> > going to generate an error even dumping/loading into the same version of
> > PostgreSQL, like 7.3 to 7.3. I don't think we want that, do we?
>
> Why are you worried? Have you counted how many SETs there are currently
> that will generate errors in older versions of PG? As long as the older
> backend will load the data correctly after rejecting the SET, there's no
> functional problem, and I think trying to hide the error is a cosmetic
> thing that will likely do more harm than good in the long run.

Fine.

You mean dumping and reloading pg_dump output in 7.3 generates errors?
I didn't know. Can you give an example? I wasn't aware of that.

--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +