| From: | "Zeugswetter Andreas DCP SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| 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:43:39 |
| Message-ID: | E1539E0ED7043848906A8FF995BDA579010545A3@m0143.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > 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.
But you can still load the dump if you execute the two statements in the
new db psql session before loading the dump file, no ?
> > > SET escape_string_warning = off;
> > > SET standard_conforming_strings = off;
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-05-17 15:45:04 | Re: Compression and on-disk sorting |
| Previous Message | Jim C. Nasby | 2006-05-17 15:41:20 | Re: Mention pg_dump version portability |