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
Views: Raw Message | Whole Thread | Download mbox
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

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2005-12-23 00:12:06 Re: Disparity in search_path SHOW and SET
Previous Message Tom Lane 2005-12-23 00:03:57 Re: Disparity in search_path SHOW and SET