| From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
|---|---|
| To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
| Cc: | marc(at)bloodnok(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: point in time recovery and moving datafiles online |
| Date: | 2002-03-08 00:53:02 |
| Message-ID: | 20020308095302I.t-ishii@sra.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
> In short, all you need is a mechanism for archiving off the WAL data and
> locating a checkpoint record in the WAL as a starting point for replay.
> Your data-file backup mechanism can be plain ol' tar or cp -r. No
> interlocks needed or wanted.
What would happen if a table is dropped or truncated while doing tar
on it? I think we do not perform any logging while doing DROP TABLE or
TRUCATE TABLE. Logging entire table would solve the problem, but that
seems to be impossible for huge tables.
Maybe we need to have some interlock mechanism to prevent DROP
TABLE/TRUNCATE/DROP DATABSE etc. while doing a backup.
--
Tatsuo Ishii
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Clift | 2002-03-08 01:01:49 | PostgreSQL for PS/2 ? |
| Previous Message | Neil Conway | 2002-03-08 00:13:12 | Re: SERIAL datatype, int or bigint? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-03-08 00:54:34 | Re: pg_class -> reltuples? |
| Previous Message | Tatsuo Ishii | 2002-03-08 00:52:57 | Re: Point in time recovery: recreating relation files |