Re: Transaction-controlled robustness for replication

From: "Marko Kreen" <markokr(at)gmail(dot)com>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Transaction-controlled robustness for replication
Date: 2008-07-22 22:39:22
Message-ID: e51f66da0807221539v2bbb75ej3b17356101510364@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 7/22/08, Simon Riggs <simon(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2008-07-22 23:08:51 Re: Transaction-controlled robustness for replication
Previous Message Simon Riggs 2008-07-22 22:18:01 Re: Plans for 8.4