Re: Synchronous replication: Admin command for replication_timeout_action - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Synchronous replication: Admin command for replication_timeout_action
Date
Msg-id 1243414504.24860.139.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: Synchronous replication: Admin command for replication_timeout_action  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On Tue, 2009-05-26 at 11:06 +0900, Fujii Masao wrote:

> Yes. Since walsender is treated as special backend, we can use
> pg_terminate_backend() to terminate replication and let the server
> standalone. This feature is simple but very useful, so I'll address it
> (my previous patch has not provided this completely yet).

I think we need something better than that. We shouldn't be shooting at
pids in a production database: we may get it wrong and take something
else down instead.

We need a graceful termination of replication and an immediate one.
There may be other things we need to add later, so a specific command
will be better and allow us to produce messages like "replication isn't
running" if used inappropriately.

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Training, Services and Support



pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: search_path vs extensions
Next
From: Peter Eisentraut
Date:
Subject: Re: [PATCH] plpythonu datatype conversion improvements