Re: Transaction-controlled robustness for replication - Mailing list pgsql-hackers

From Marko Kreen
Subject Re: Transaction-controlled robustness for replication
Date
Msg-id e51f66da0807221539v2bbb75ej3b17356101510364@mail.gmail.com
Whole thread Raw
In response to Transaction-controlled robustness for replication  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: Transaction-controlled robustness for replication  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
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?

-- 
marko


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Plans for 8.4
Next
From: Simon Riggs
Date:
Subject: Re: Transaction-controlled robustness for replication