Re: Transaction-controlled robustness for replication

On Wed, 2008-07-23 at 01:39 +0300, Marko Kreen wrote:
> On 7/22/08, Simon Riggs <simon@2ndquadrant.com> wrote:
> >  We could represent this with 3 parameters:
> >  synchronous_commit = on | off
> >  synchronous_standby_transfer = on | off
> >  synchronous_standby_wal_fsync = on | off
> >
> >  If we are able to define these robustness characteristics for each
> >  transaction *separately* then it will represent an industry first: no
> >  other database has that capability implemented or planned on published
> >  roadmaps, nor has it been discussed in research to my knowledge.
> >
> >  Changing the parameter setting at transaction-level would be expensive
> >  if we had to set three parameters.
> 
> How about extending BEGIN.with additional keywords?

SQL Standard, plus many interfaces hide BEGIN from you.

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Training, Services and Support