Re: [HACKERS] WAL logging of heap_mark4update

2005-01-16 Thread Tom Lane
Heikki Linnakangas <[EMAIL PROTECTED]> writes: > On Sat, 15 Jan 2005, Tom Lane wrote: >> Right. The 2PC connection is another reason to do it that way --- 2PC >> would require some way to save locks anyhow, and it'd be nice if there >> were only one mechanism to deal with not two. > AFAICS, heap_

Re: [HACKERS] WAL logging of heap_mark4update

2005-01-16 Thread Heikki Linnakangas
On Sat, 15 Jan 2005, Tom Lane wrote: Alvaro Herrera <[EMAIL PROTECTED]> writes: Hackers, In access/heap/heapam.c, in heap_mark4update(), there's a comment that states /* * XLOG stuff: no logging is required as long as we have no * savepoints. For savepoints private log co

Re: [HACKERS] WAL logging of heap_mark4update

2005-01-15 Thread Tom Lane
Alvaro Herrera <[EMAIL PROTECTED]> writes: > Hackers, > In access/heap/heapam.c, in heap_mark4update(), there's a comment that > states > /* >* XLOG stuff: no logging is required as long as we have no >* savepoints. For savepoints private log could be used... >*/ > I