From: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
Cc: | Alexander Reichstadt <info(at)apfeltaste(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Export and import from one postgres server to another |
Date: | 2012-05-30 03:55:01 |
Message-ID: | 4FC59A15.6020903@ringerc.id.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 05/30/2012 10:01 AM, Adrian Klaver wrote:
> On 05/29/2012 06:56 PM, Craig Ringer wrote:
>> On 05/29/2012 02:27 AM, Alexander Reichstadt wrote:
>>> Hi,
>>>
>>> I am trying to "simply" export my postgres database from one server
>>> and then import it into another. I thought I could use PhpPgAdmin,
>>> but the hints on the web don't seem to work. One said to simply get
>>> a dump from one phpPgAdmin, the go to the other server, select the
>>> database, click the SQL button and then select the dump file. When I
>>> do this the import fails because the dump file begins with a
>>> \connect statement.
>>
>> I don't really know why pg_dump includes that \connect , but it isn't
>> the only problem you'll hit with that approach. PgAdmin-III seems to
>> wrap the invoked SQL in a transaction, and the dump will try to
>> (re)-create the `postgres' role, which will fail and abort the
>> transaction.
>
> Well just to keep the confusion level down a bit, the OP was referring
> to phpPgAdmin:)
Argh, I missed that. Thanks very much for spotting and correcting it.
--
Craig Ringer
From | Date | Subject | |
---|---|---|---|
Next Message | yi huang | 2012-05-30 04:36:23 | Re: How to handle nested record data. |
Previous Message | Pavel Stehule | 2012-05-30 03:21:03 | Re: How to handle nested record data. |