From: | Malcolm Warren <malcolm(at)villeinitalia(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Creating new database - SOLVED |
Date: | 2009-11-18 17:05:35 |
Message-ID: | 4B04295F.6070901@villeinitalia.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Dear All,
Thank you for your emails which were very helpful.
I've finally solved it.
template1 was full of data, presumably somehow from a badly-run dump and
restore.
So when I created the new database, that too was full of data from the
template.
I ran a clean pg_dump on template1 from my production database and
restored it on my test machine, and finally everything is normal.
Thanks again,
Malcolm
Joao Ferreira gmail ha scritto:
> On Wed, 2009-11-18 at 08:39 -0700, Scott Marlowe wrote:
>
>> On Wed, Nov 18, 2009 at 8:12 AM, Joao Ferreira gmail
>> <joao(dot)miguel(dot)c(dot)ferreira(at)gmail(dot)com> wrote:
>>
>>> I'dd suggest:
>>>
>>> pgdumpall --clean > dump.sql
>>>
>> I'd think he'd be much better off with pg_dump, not pg_dumpall.
>>
>
> yes, agree. sorry.
>
> joao
>
>
>> pg_dump srcdb | psql destdb
>>
>> you can add -s as a pg_dump switch if all you want is the schema.
>>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2009-11-18 17:13:38 | Re: passing parameters to multiple statements |
Previous Message | doug livesey | 2009-11-18 17:02:38 | Re: Totally fresh uninstall/reinstall of Postgres on MacBook Pro running Snow Leopard? |