| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Rich Shepard <rshepard(at)appl-ecosys(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Table update: restore or replace? |
| Date: | 2019-05-14 21:10:39 |
| Message-ID: | 28923.1557868239@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
> If you where to restore at the file level I would:
> 1) Stop the server.
> 2) Move the existing content of /var/lib/pgsql/10/data/ somewhere else
> just to be safe.
> 3) Copy in the backup.
Yeah. You can't just selectively copy files, because the data files
are dependent on the contents of the pg_xact transaction log; it's
all or nothing.
Also, I don't know what method you've been using to make file-level
backups, but they're really pretty worthless unless you (a) stop
the server or (b) use a filesystem snapshot. Otherwise you're very
likely to have inconsistent data.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rich Shepard | 2019-05-14 21:19:44 | Re: Table update: restore or replace? |
| Previous Message | Adrian Klaver | 2019-05-14 21:05:58 | Re: Table update: restore or replace? |