Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and - Mailing list pgsql-hackers

From Qingqing Zhou
Subject Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and
Date
Msg-id dofett$eat$1@news.hub.org
Whole thread Raw
In response to WAL bypass for INSERT, UPDATE and DELETE?  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and
List pgsql-hackers
"Qingqing Zhou" <zhouqq@cs.toronto.edu> wrote
>
>
> To make things, is it possible to add a GUC to let user disable *all* the 
> xlogs?
>

It may work like this:

BEGIN TRANSACTION WITHOUT XLOG;    /* forbidden vacuum, PITR etc */
BEGIN
...    /* no xlog during this peroid */
END;   /* don't mark this transaction committed */
BEGIN
...
END;
END TRANSACTION DO COMMIT;    /* at this time issue checkpiont && mark all 
transactions committed */

So during this peroid, if any transaction failed, the only consequence is 
add invisible garbage data. When everything is going well, then END 
TRANSACTION DO COMMIT will mark these transaction permanate. Also, seems 
there is no problem even with XLOG_NO_TRAN updates.

Regards,
Qingqing




pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: PL/pgSQL proposal: using list of scalars in assign
Next
From: Ashok Agrawal
Date:
Subject: Re: Oracle PL/SQL Anonymous block equivalent in postgres