[EMAIL PROTECTED] wrote:
> I've run into a problem while migrating an existing 8.2.7 data base to a
> new server running 8.3.3 (although I think the version numbers may not
> matter -- I think I've seen this problem in the past and just lived with
> it since so much of Postgresql is so great!).
>
Tom Lane wrote:
> [EMAIL PROTECTED] writes:
>> Thus, when piping the output (from legacy host 192.168.2.2) to
>> populate the newly initialized cluster, by way of running (on the new
>> host 192.168.2.3)
>> pg_dumpall -h 192.168.2.2|psql
>> an error occurs in that first section when the s
Tom Lane wrote:
> [EMAIL PROTECTED] writes:
>> Thus, when piping the output (from legacy host 192.168.2.2) to
>> populate the newly initialized cluster, by way of running (on
the new
>> host 192.168.2.3)
>> pg_dumpall -h 192.168.2.2|psql
>> an error occurs in that first sectio
[EMAIL PROTECTED] writes:
> Thus, when piping the output (from legacy host 192.168.2.2) to
> populate the newly initialized cluster, by way of running (on the new
> host 192.168.2.3)
> pg_dumpall -h 192.168.2.2|psql
> an error occurs in that first section when the script attempts to
> se
- Original Message -
From:
Patrick
Hatcher
To: [EMAIL PROTECTED]
Sent: Thursday, November 20, 2003 12:34
AM
Subject: [GENERAL] Pg_dumpall
problem
Did a pg_dumpall from my production database (7.3.2) and I tried to
restoreto my Dev database (7.4). I
