| From: | "Zeugswetter Andreas DCP SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump and backslash escapes |
| Date: | 2006-05-17 15:27:33 |
| Message-ID: | E1539E0ED7043848906A8FF995BDA5790105459E@m0143.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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 ?
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-05-17 15:29:30 | Re: pg_dump and backslash escapes |
| Previous Message | Tom Lane | 2006-05-17 15:19:48 | Re: Foreign key column reference ordering and information_schema |