Re: Postgres-R: internal messaging - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Postgres-R: internal messaging
Date
Msg-id 11514.1216846302@sss.pgh.pa.us
Whole thread Raw
In response to Re: Postgres-R: internal messaging  (Markus Wanner <markus@bluegap.ch>)
Responses Re: Postgres-R: internal messaging  (Markus Wanner <markus@bluegap.ch>)
List pgsql-hackers
Markus Wanner <markus@bluegap.ch> writes:
> ... crashes are more difficult. IMO the replication 
> manager needs to stay alive during this reinitialization, to keep the 
> GCS connection. However, it can easily detach from shared memory 
> temporarily (the imessages stuff is the only shmem place it touches, 
> IIRC). However, a more difficult aspect is: it must be able to tell if a 
> backend has applied its transaction *before* it died or not. Thus, after 
> all backends have been killed, the postmaster needs to wait with 
> reinitializing shared memory, until the replication manager has consumed 
> all its messages. (Otherwise we would risk "losing" local transactions, 
> probably also remote ones).

I hope you're not expecting the contents of shared memory to still be
trustworthy after a backend crash.  If the manager is working strictly
from its own local memory, then it would be reasonable to operate
as above.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Manoel Henrique"
Date:
Subject: Re: Research/Implementation of Nested Loop Join optimization
Next
From: Andrew Dunstan
Date:
Subject: Re: [PATCHES] odd output in restore mode