| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: version mismatch message |
| Date: | 2003-07-31 16:57:48 |
| Message-ID: | Pine.LNX.4.56.0307311855410.2039@krusty.credativ.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane writes:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Nonetheless, I think a pg_dump 7.3.2 dumping a 7.3.3 database should not
> > raise a version mismatch message at all.
>
> I'm unconvinced; at best, you are assuming zero bugs.
Yes. The version mismatch message wasn't created because we are assuming
bugs, but because we know that pg_dump cannot handle the catalogs, which
is not the case when you use 7.3.2 to dump 7.3.3. If we want to take bugs
into account, then we can't let pg_dump work with any other version,
possibly not even its own.
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-07-31 17:28:24 | Re: Another nasty pg_dump problem |
| Previous Message | Josh Berkus | 2003-07-31 16:48:18 | Re: followup on previous |