Re: pg_dump and backslash escapes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump and backslash escapes
Date: 2006-05-17 14:47:20
Message-ID: 19971.1147877240@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-05-17 14:54:26 Re: What default is - SET behavior
Previous Message Simon Riggs 2006-05-17 14:40:35 Re: does wal archiving block the current client connection?