| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Andres Freund" <andres(at)anarazel(dot)de>, <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
| Subject: | Re: unlogged tables |
| Date: | 2010-11-16 22:36:12 |
| Message-ID: | 4CE2B2FC020000250003785D@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> wrote:
> One way your backup runs too long and too much data changes, the
> other way round you loose the data which you assumed safely
> backuped.
>
> Isn't that a *really* easy decision?
Yeah. Count me in the camp which wants the default behavior to be
that pg_dump backs up all permanent tables, even those which aren't
WAL-logged (and therefore aren't kept up in PITR backups, hot/warm
standbys, or streaming replication).
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-11-16 22:38:48 | Re: Per-column collation |
| Previous Message | Andres Freund | 2010-11-16 22:30:29 | Re: unlogged tables |