| From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Mark Kirkwood" <markir(at)coretech(dot)co(dot)nz> |
| Cc: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Point in Time Recovery |
| Date: | 2004-07-30 07:57:26 |
| Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA40184D170@m0114.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > I was wondering about this point - might it not be just as reasonable
> > for the copied file to *be* an exact image of pg_control? Then a very
> > simple variant of pg_controldata (or maybe even just adding switches to
> > pg_controldata itself) would enable the relevant info to be extracted
>
> We didn't do that so admins could easily read the file contents.
If you use a readable file you will also need a feature for restore (or a tool)
to create an appropriate pg_control file, or are you intending to still require
that pg_control be the first file backed up.
Another possibility would be that the start function writes the readable file and
also copies pg_control.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Hallgren | 2004-07-30 11:14:38 | Re: try/catch macros for Postgres backend |
| Previous Message | Mamta Singh | 2004-07-30 07:01:29 | Regarding the logging in Postgres |