Synchronous replication: Promotion of Standby to Primary

From: "K, Niranjan (NSN - IN/Bangalore)" <niranjan(dot)k(at)nsn(dot)com>
To: "ext Fujii Masao" <masao(dot)fujii(at)gmail(dot)com>
Cc: "Kolb, Harald (NSN - DE/Munich)" <harald(dot)kolb(at)nsn(dot)com>, "Czichy, Thoralf (NSN - FI/Helsinki)" <thoralf(dot)czichy(at)nsn(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Synchronous replication: Promotion of Standby to Primary
Date: 2009-05-04 14:07:45
Message-ID: 985D3C447786074E957A9001D62CDDD05A367A@SGSIEXC009.nsn-intra.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

Re-opening the discussion related to triggers to promote standby server.
In the earlier dicussion, there were 2 proposals, Trigger based on file
and trigger based on signals. I think there was no conclusion on this.
http://archives.postgresql.org/pgsql-hackers/2008-12/msg01231.php

According to the proposal, it seems to be better if signals are used as
we can avoid checking the file existance in the loop. Or the other
approach is to use inotify (http://en.wikipedia.org/wiki/Inotify) But
portability to other unix like OS is an issue to look for.

Could you please get back which is being implemented/ considered for
promotion of standby?

regards,
Niranjan

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2009-05-04 14:10:49 conditional dropping of columns/constraints
Previous Message Tom Lane 2009-05-04 12:57:35 Re: "could not reattach to shared memory" captured in buildfarm