Re: Enhancement to pg_dump

From: Rob Kirkbride <rob(dot)kirkbride(at)gmail(dot)com>
To: Richard Huxton <dev(at)archonet(dot)com>
Cc: Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Enhancement to pg_dump
Date: 2008-11-26 10:34:20
Message-ID: 492D262C.5090405@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Richard,

Yes, I've changed it use TRUNCATE rather than DELETE and it's working
well for us now.

The switching of the database is a good idea - thanks. Unfortunately,
we've not got enough disk space currently to do that, but if we get
problems in the future that will definitely be something we'll consider.

Rob

Richard Huxton wrote:
> Rob Kirkbride wrote:
>
>> I've introduced a --delete-not-drop option which simply does a DELETE FROM %
>> rather than 'DROP and then CREATE'.
>>
>
> Beware foreign-keys slowing you - TRUNCATE all relevant tables should be
> the fastest method if possible.
>
>
>> I hope this sounds sensible and I haven't missed something - I'm still
>> learning!
>>
>
> Have you considered restoring to a completely different database
> (report1/report2) and just switching between them?
>
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hitoshi Harada 2008-11-26 10:43:35 Re: Windowing Function Patch Review -> Standard Conformance
Previous Message Pavan Deolasee 2008-11-26 10:22:35 Re: Review: Hot standby