Re: Hot Standby Design

From: "Dave Page" <dpage(at)pgadmin(dot)org>
To: "Robert Treat" <xzilla(at)users(dot)sourceforge(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, "Simon Riggs" <simon(at)2ndquadrant(dot)com>
Subject: Re: Hot Standby Design
Date: 2008-09-24 07:28:21
Message-ID: 937d27e10809240028q1bb93f87w8202f8edd7885e3d@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 24, 2008 at 5:30 AM, Robert Treat
<xzilla(at)users(dot)sourceforge(dot)net> wrote:

> I presume this means the backend kill function would work? Also, can you go
> into why pgAgent would not work? (I presume it's because you can't update
> information that needs to be changed when jobs run, if thats the case it
> might be worth thinking about making pgAgent work across different clusters)

Probably - it needs to be able to update its catalogs to record job
results and ensure that only a single node runs any given job
instance.

We could probably update the code to optionally accept a connection
string instead of a database name, which would allow us to operate
against servers other than the one with the catalogs installed.

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2008-09-24 07:37:36 Re: Hot Standby Design
Previous Message Simon Riggs 2008-09-24 07:27:44 Re: Hot Standby Design