From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, "Ed L(dot)" <pgsql(at)bluepolka(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: pgsql client/server compatibility matrix? |
Date: | 2005-07-26 14:56:20 |
Message-ID: | 1122389780.15145.64.camel@state.g2switchworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 2005-07-26 at 09:26, Tom Lane wrote:
> Scott Marlowe <smarlowe(at)g2switchworks(dot)com> writes:
> > On Mon, 2005-07-25 at 22:02, Tom Lane wrote:
> >> pg_dump believes it can dump from any server back to 7.0; if it can't,
> >> that's a bug, and details would be appreciated.
>
> > I thought the backwards dumping compatibility thing was fairly new (i.e.
> > it showed up around 7.3 or 7.4) and before that, if you used, say
> > pg_dump from 7.1 to try and dump from 6.5 you'd get errors.
>
> That was true back in the 6.x days, but starting in 7.1 we had code in
> pg_dump to work with a 7.0 server, and we've kept up that policy.
>
> Perhaps you are thinking of pg_dumpall specifically? That was a shell
> script until 7.3, and before it was converted to C I don't think it had
> much of any cross-version adaptability.
Ding! That was it. I knew something had bitten me back in the day, but
honestly, 7.2 is a fast fading memory.
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2005-07-26 15:12:41 | Re: transaction timeout |
Previous Message | Dr NoName | 2005-07-26 14:40:30 | transaction timeout |