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

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and
Date: 2005-12-23 04:31:07
Message-ID: 15810.1135312267@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
"Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu> writes:
> I guess I know (at least part) of what you mean. This is because we rely on 
> replay all the xlog no matter it belongs to a committed transaction or not. 
> Why? Because a failed transaction is not totally useless since later 
> transaction may reply on some physical thing it creates - for example, a new 
> page and its links of a btree. So for heap, there is(95% sure) no such 
> problem.

Torn pages (partial page write) are still a problem.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Christopher Kings-LynneDate: 2005-12-23 05:19:31
Subject: Re: [pgadmin-hackers] Client-side password encryption
Previous:From: Tom LaneDate: 2005-12-23 04:13:07
Subject: Re: [pgadmin-hackers] Client-side password encryption

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