Re: pg_dump and backslash escapes

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Zeugswetter Andreas DCP SD <ZeugswetterA(at)spardat(dot)at>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump and backslash escapes
Date: 2006-05-18 16:08:09
Message-ID: 200605181608.k4IG89K09942@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Greg Stark wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>
> > Zeugswetter Andreas DCP SD wrote:
> >
> > > I thought the suggested procedure (see migration doc) was to use the
> > > new pg_dump to dump the older db version, so why backpatch ?
> >
> > Uh, you can suggest it, but I would guess < 50% do it, and once the old
> > database is gone, there is no way to re-do the dump.
>
> I thought the plan was to have one version that supported
> standards_conforming_strings but defaulted to false anyways. So this would
> only bite people who were jumping over an entire major release.

Yes, that is true.

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

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim C. Nasby 2006-05-18 16:18:51 Re: Compression and on-disk sorting
Previous Message Thomas Hallgren 2006-05-18 16:07:18 Re: Question about casts