Re: Proposal: Commit timestamp - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Proposal: Commit timestamp
Date
Msg-id 200702082032.l18KWfr01501@momjian.us
Whole thread Raw
In response to Re: Proposal: Commit timestamp  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Proposal: Commit timestamp  (Jan Wieck <JanWieck@Yahoo.com>)
List pgsql-hackers
Alvaro Herrera wrote:
> > > Is this a new policy that after discussion, all patches must be 
> > > resubmitted with a summary and conclusions of the discussion? I can 
> > > certainly do that for you, but just tell me if you are going to ask the 
> > > same from everyone.
> > 
> > No, I am asking only this time because I feel there was too much
> > disconnect between the patch and the extensive replication discussion
> > that few community members would see the connection.
> 
> FYI, in my opinion the trigger addition is clearly useful to Mammoth
> Replicator as well.  In fact, it's so obviously useful that I didn't see
> a need to state that in the original thread where it was discussed.

Right, I know it is useful too, but I would like a layout of what it
does and why so everyone is clear on it.

--  Bruce Momjian  <bruce@momjian.us>          http://momjian.us EnterpriseDB
http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Marc Munro
Date:
Subject: Re: referential Integrity and SHARE locks
Next
From: Tom Lane
Date:
Subject: Re: [PATCHES] [pgsql-patches] Phantom Command IDs, updated patch