On 12/27/10 11:44 AM, Tom Lane wrote:
Right, but the key word in that sentence is "forwards". Dumping from an
8.3 database with 9.0 pg_dump will likely produce SQL that doesn't
reload into an 8.3 server, only into 9.0.
heh, thats what I was trying to say, before my first cup of coffee :)
sorry
Le 27/12/2010 20:38, John R Pierce a écrit :
> On 12/27/10 11:00 AM, Guillaume Lelarge wrote:
>> Le 27/12/2010 18:27, Gauthier, Dave a écrit :
>>> Hi:
>>>
>>> I'm working with 2 different PG installs on 2 different linux
>>> servers, one running v9.0.1 and the other v8.3.4. The older install
>>> i
John R Pierce writes:
> On 12/27/10 11:00 AM, Guillaume Lelarge wrote:
>> psql should work the same, apart from new metacommands. I don't think
>> you'll experience issues with pg_ctl. I would not recommend you to user
>> pg_dump and pg_restore. They are pretty sensitive to the PostgreSQL release.
On 12/27/10 11:00 AM, Guillaume Lelarge wrote:
Le 27/12/2010 18:27, Gauthier, Dave a écrit :
Hi:
I'm working with 2 different PG installs on 2 different linux servers, one running v9.0.1
and the other v8.3.4. The older install is "frozen" for the project (which is
nearing completion) for env
Le 27/12/2010 18:27, Gauthier, Dave a écrit :
> Hi:
>
> I'm working with 2 different PG installs on 2 different linux servers, one
> running v9.0.1 and the other v8.3.4. The older install is "frozen" for the
> project (which is nearing completion) for environment stability reasons.
> This is
Hi:
I'm working with 2 different PG installs on 2 different linux servers, one
running v9.0.1 and the other v8.3.4. The older install is "frozen" for the
project (which is nearing completion) for environment stability reasons. This
is out of my control. I cannot upgrade v8.3.4 on that server
