[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!).
The
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!).
The problem stems from the fact
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!).
The problem stems from the
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 script
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
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!).
The problem stems from the
[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
set a
