Skip site navigation (1) Skip section navigation (2)

Re: recovery.conf location

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: (view raw, whole thread or download thread mbox)
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

In response to


pgsql-hackers by date

Next:From: Andrew GeeryDate: 2010-09-30 03:05:11
Subject: starting to review the Extend NOT NULL representation to pg_constraint patch
Previous:From: Josh KupershmidtDate: 2010-09-30 02:41:01
Subject: Re: I: About "Our CLUSTER implementation is pessimal" patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group