Tom Lane wrote:
"Joshua D. Drake" writes:
On Tue, 2009-04-14 at 09:58 -0700, Roderick A. Anderson wrote:
The plan calls for a pg_dump using my workstation using CREATE the
database and INSERTS (-C -D) . Then use psql to run the script created
above to build the database on the new system.
Joshua D. Drake wrote:
On Tue, 2009-04-14 at 09:58 -0700, Roderick A. Anderson wrote:
I can't avoid it any longer and have to move an old RT2 installation to
a new machine. (I'll upgrade to RT3 on that machine.)
The plan calls for a pg_dump using my workstation using CREATE the
database and
John R Pierce wrote:
Roderick A. Anderson wrote:
make sure pg_hba.conf on the old machine allows you to connect from the
new machine's IP address as the user postgres (this may require setting
a database password for the postgres user on the old machine if the
'host' authentication method
Roderick A. Anderson wrote:
I can't avoid it any longer and have to move an old RT2 installation
to a new machine. (I'll upgrade to RT3 on that machine.)
The plan calls for a pg_dump using my workstation using CREATE the
database and INSERTS (-C -D) . Then use psql to run the script
created
"Joshua D. Drake" writes:
> On Tue, 2009-04-14 at 09:58 -0700, Roderick A. Anderson wrote:
>> The plan calls for a pg_dump using my workstation using CREATE the
>> database and INSERTS (-C -D) . Then use psql to run the script created
>> above to build the database on the new system.
> You wan
On Tue, 2009-04-14 at 09:58 -0700, Roderick A. Anderson wrote:
> I can't avoid it any longer and have to move an old RT2 installation to
> a new machine. (I'll upgrade to RT3 on that machine.)
>
> The plan calls for a pg_dump using my workstation using CREATE the
> database and INSERTS (-C -D)
I can't avoid it any longer and have to move an old RT2 installation to
a new machine. (I'll upgrade to RT3 on that machine.)
The plan calls for a pg_dump using my workstation using CREATE the
database and INSERTS (-C -D) . Then use psql to run the script created
above to build the database
