Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and
- From: Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>
- To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: pgsql-hackers(at)postgresql(dot)org
- Subject: Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and
- Date: Fri, 23 Dec 2005 21:37:42 -0500 (EST)
- Message-id: <Pine(dot)LNX(dot)4(dot)58(dot)0512232135140(dot)24800(at)eon(dot)cs>
>
> Torn pages (partial page write) are still a problem.
I revised the idea with MINIMAL XLOG (instead of WITHOUT XLOG) like the
below. I think in this way, we can always gaurantee its correctness and
can always improve it.
To Use It
----------
A "BEGIN TRANSACTION MINIMAL XLOG/END" block is a speicial "BEGIN/END"
transaction block. It tries to avoid unnessary xlogs but still perserves
transaction semantics. It is good for the situation that the user wants to
do a big data load. It is issued like this:
1. BEGIN TRANSACTION MINIMAL XLOG
2. ... /* statements */
3. END;
Home |
Main Index |
Thread Index