From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: s/recovery_connections/allow_standby_queries/, or something like that? |
Date: | 2010-04-29 18:11:43 |
Message-ID: | 4BD9CBDF.7030107@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Huh, that is an interesting point. I think it might eventually be a
> common use case: when you're trying to determine where to stop a PITR
> recovery, it would be really nice to be able to roll forward to some
> point, pause the recovery, and then snoop around in the database in
> a read-only fashion before deciding whether to advance further. We
> don't currently have a good mechanism for the pause-and-resume bit
> but I bet something like walreceiver could be built to do that.
> The "snoop around" part is already handled nicely by HS.
Yeah, it's too bad we never got around to fix the pause/resume functions
the original HS patch included.
>> +1 on changing it to something.
>
> Any thoughts on what?
Well, the obvious possibility is:
hot_standby = on/off
allow_recovery_queries? Not sure I like either of those more than
allow_standby_queries, though, despite what I just wrote.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2010-04-29 18:12:34 | Re: Re: [COMMITTERS] pgsql: Make CheckRequiredParameterValues() depend upon correct |
Previous Message | Chris Browne | 2010-04-29 18:06:36 | Re: Add column if not exists (CINE) |