Re: pg_dump --comment? - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: pg_dump --comment?
Date
Msg-id 40B75158.7090309@dunslane.net
Whole thread Raw
In response to Re: pg_dump --comment?  (Jon Jensen <jon@endpoint.com>)
Responses Re: pg_dump --comment?  (James Robinson <jlrobins@socialserve.com>)
List pgsql-hackers
Jon Jensen wrote:

>On Fri, 28 May 2004, Christopher Kings-Lynne wrote:
>
>  
>
>>>I've encountered a situation where I'd like to store some information 
>>>about the database when I do a pg_dump. For instance, the timestamp of 
>>>the dump. And some other information that I pull from the database.
>>>      
>>>
>>I think every dump should dump the timestamp regardless...
>>    
>>
>
>That would cause me a lot of trouble. Every night I do a pg_dump on all my
>databases to a temporary file. Then I use cmp to compare that dump to last
>night's dump. If they're identical I just delete the new dump so that only
>the old one remains, with its original timestamp. That way rsync doesn't
>see any change, and doesn't waste any time comparing it when we do
>backups. It's also handy to see the last day the dump changed by looking
>at the file's timestamp.
>
>Granted, this is only of interest on databases that don't change at all, 
>but on a multi-user system we have a surprising number of databases that 
>don't change at all for days (alongside the ones that change all the time, 
>of course).
>
>However, I would like to see an option to include the timestamp if someone 
>wants it.
>
>  
>

That makes sense.

A better answer to this particular problem might be incremental dumps, 
though :-)

cheers

andrew


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: On query rewrite
Next
From: Andrew Dunstan
Date:
Subject: Re: Win32, PITR, nested transactions, tablespaces