[pg_rewind] Request for command line switch to prevent removal of stored procedures - Mailing list pgsql-cluster-hackers

From Rainer Brestan
Subject [pg_rewind] Request for command line switch to prevent removal of stored procedures
Date
Msg-id trinity-dec9e13c-22a3-4d29-9953-d7f6fc84a18c-1439806609964@3capp-gmx-bs18
Whole thread Raw
List pgsql-cluster-hackers
<div style="font-family: Verdana;font-size: 12.0px;"><div>pg_rewind installes stored procedures at begin and remove
themafter end of operation.</div><div>This makes it impossible to run twice
simultaneously.</div><div> </div><div>pg_rewindis a useful extension for Pacemaker clusters.</div><div>It makes it
possibleto demote and sync automatically to the new master (when it is promoted), because it needs only few
seconds.</div><div>Therefore,this feature can be integrated in the psql resource agent.</div><div> </div><div>But it is
impossiblefor the resource agent to guarantee only one node will cann pg_rewind at the same time.</div><div>Especially
whenthe Postgres resource is in different clusters configured.</div><div>One slave (which calls pg_rewind) will remove
thestored procedures another slave is accessing.</div><div> </div><div>Would it be possible to add a command line
switchto pg_rewind, which does not remove the stored procedures at end of operation and check for existance on start
?</div><div>Defaultis to remove at end.</div><div> </div><div>In case we use pg_rewind with Pacemaker, it is harmless
existingall the time in the database.</div><div>And we can integrate a recover feature into Pacemaker for Postgres
resources.</div><div> </div><div>Rainer</div></div>

pgsql-cluster-hackers by date:

Previous
From: Genc, Ömer
Date:
Subject: Design of live and archive database
Next
From: FattahRozzaq
Date:
Subject: Can we limit the total size of WAL?