| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Jaime Casanova <jaime(at)2ndquadrant(dot)com>, Thom Brown <thom(at)linux(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: recovery.conf location |
| Date: | 2010-09-30 02:54:19 |
| Message-ID: | 25712.1285815259@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> But that's not what Tom is talking about, I don't think: you might
> also want a way to explicitly whack the flag in pg_control around.
> That would probably be along the lines of pg_resetxlog. I'm not sure
> how much use case there is for such a thing, but if it's needed it's
> certainly wouldn't be hard to write.
Right, but instead of having to provide such a tool, we could just
store the status as a text file. There is a pretty time-honored
tradition for that, ya know.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Geery | 2010-09-30 03:05:11 | starting to review the Extend NOT NULL representation to pg_constraint patch |
| Previous Message | Josh Kupershmidt | 2010-09-30 02:41:01 | Re: I: About "Our CLUSTER implementation is pessimal" patch |