| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thom Brown <thombrown(at)gmail(dot)com> |
| Cc: | jd(at)commandprompt(dot)com, PGSQL Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_dump custom format across versions |
| Date: | 2010-05-12 19:18:59 |
| Message-ID: | 4014.1273691939@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thom Brown <thombrown(at)gmail(dot)com> writes:
> On 12 May 2010 19:40, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
>>> Am I to gather that there are possible incompatibilities?
>>
>> Definitely.
> In that case, it might be an idea to clarify that on the documentation. I
> couldn't find this information.
If it were true, it would be in the documentation.
The reason for suggesting that you use the newer pg_dump during a
version upgrade is that the newer version might have bug fixes that
your current version lacks. In the absence of bugs, however, pg_restore
is supposed to read dump files produced by older versions of pg_dump.
If it fails to, that in itself is a filable bug.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2010-05-12 20:46:17 | Re: [ANNOUNCE] Bug-fix and new feature of pg_lesslog is released |
| Previous Message | Thom Brown | 2010-05-12 18:45:12 | Re: pg_dump custom format across versions |