| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| 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 04:41:29 |
| Message-ID: | 87lkt0osg6.fsf@stark.xeocode.com |
| 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:
> 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.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-05-18 04:45:11 | Re: does wal archiving block the current client connection? |
| Previous Message | Jeff Frost | 2006-05-18 04:39:40 | Re: does wal archiving block the current client connection? |