Re: failover vs. read only queries - Mailing list pgsql-hackers

From Takahiro Itagaki
Subject Re: failover vs. read only queries
Date
Msg-id 20100610095804.9888.52131E4D@oss.ntt.co.jp
Whole thread Raw
In response to Re: failover vs. read only queries  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: failover vs. read only queries
List pgsql-hackers
Fujii Masao <masao.fujii@gmail.com> wrote:

> > 1. Reset max_standby_delay = 0 in postgresql.conf
> > 2. pg_ctl reload
> > 3. Create a trigger file
> 
> As far as I read the HS code, SIGHUP is not checked while a recovery
> is waiting for queries :(  So pg_ctl reload would have no effect on
> the conflicting queries.
> 
> Independently from the problem I raised, I think that we should call
> HandleStartupProcInterrupts() in that sleep loop.

Hmmm, if reload doesn't work, can we write a query like below?
 SELECT pg_terminate_backend(pid)   FROM pg_locks  WHERE conflicted-with-recovery-process;

Regards,
---
Takahiro Itagaki
NTT Open Source Software Center




pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: parser handling of large object OIDs
Next
From: David Gardner
Date:
Subject: 'create or replace function' no longer allows parameters