Re: pg_dump and backslash escapes - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_dump and backslash escapes
Date
Msg-id 19971.1147877240@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_dump and backslash escapes  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: pg_dump and backslash escapes
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> 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.

Well, looking at the SETs already currently emitted:

$ pg_dump -s regression | grep ^SET
SET client_encoding = 'SQL_ASCII';    fails before 7.1
SET check_function_bodies = false;    fails before 7.4
SET client_min_messages = warning;    fails before 7.3
SET search_path = public, pg_catalog;    fails before 7.3
SET default_tablespace = '';        fails before 8.0
SET default_with_oids = false;        fails before 8.0

so I'm not at all clear what you've got against this one.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: PL/pgSQL 'i = i + 1' Syntax
Next
From: Tom Lane
Date:
Subject: Re: What default is - SET behavior