Skip site navigation (1) Skip section navigation (2)

Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and

From: "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and
Date: 2005-12-23 00:05:10
Message-ID: dofett$eat$1@news.hub.org (view raw or flat)
Thread:
Lists: pgsql-hackers
"Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)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



In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2005-12-23 00:12:06
Subject: Re: Disparity in search_path SHOW and SET
Previous:From: Tom LaneDate: 2005-12-23 00:03:57
Subject: Re: Disparity in search_path SHOW and SET

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group