From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Zeugswetter Andreas DCP SD <ZeugswetterA(at)spardat(dot)at> |
Cc: | 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-17 15:29:30 |
Message-ID: | 200605171529.k4HFTU016679@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Zeugswetter Andreas DCP SD wrote:
>
> > Very clear. The issue is that I can't find any of these emitted by a
> > pg_dump version who's native backend doesn't understand them.
> >
> > I assume that it is expected that a cross-db dump/reload will generate
> > errors, and it is done rarely for upgrades, but I assume same-version
> > dump/restore is done more frequently and people don't expect errors.
> > Is that not a significant distinction?
>
> 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.
--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-05-17 15:32:52 | Re: pg_dump and backslash escapes |
Previous Message | Zeugswetter Andreas DCP SD | 2006-05-17 15:27:33 | Re: pg_dump and backslash escapes |