Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database"
Date
Msg-id 50E609F7.30405@commandprompt.com
Whole thread Raw
In response to Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database"  ("Kevin Grittner" <kgrittn@mail.com>)
List pgsql-hackers
On 01/03/2013 02:30 PM, Kevin Grittner wrote:
>
> Andrew Dunstan wrote:
>
>> I don't especially have a horse in the race, but ISTM that if you want
>> the information you want it to be able to persist across dump/restore,
>> at least optionally. If you can happily lose it when you're forced to
>> recover using a logical dump then it's not that important to you.
>
> On that point I guess we will just disagree. In my experience, if
> you are OK with a periodic pg_dump for your primary backup
> technique, then the data is just not that important to you.

Or the data doesn't change that much but in principle I agree with you.

JD


-- 
Command Prompt, Inc. - http://www.commandprompt.com/
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC
@cmdpromptinc - 509-416-6579



pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database"
Next
From: Tom Lane
Date:
Subject: Re: pg_upgrade test script creates port conflicts in parallel testing