| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)mail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Christopher Browne <cbbrowne(at)gmail(dot)com>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Andres Freund <andres(at)2ndquadrant(dot)com>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" |
| Date: | 2013-01-03 22:45:11 |
| Message-ID: | 50E609F7.30405@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-01-03 22:57:01 | Re: pg_upgrade test script creates port conflicts in parallel testing |
| Previous Message | Kevin Grittner | 2013-01-03 22:30:49 | Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" |