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

Re: Moving more work outside WALInsertLock

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Moving more work outside WALInsertLock
Date: 2011-12-15 15:34:55
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> I've been experimenting with different approaches to do that, but one 
> thing is common among all of them: you need to know the total amount of 
> WAL space needed for the record, including backup blocks, before you 
> take the lock. So, here's a patch to move things around in XLogInsert() 
> a bit, to accomplish that.

This patch may or may not be useful, but this description of it is utter
nonsense, because we already do compute that before taking the lock.
Please try again to explain what you're doing?

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Dimitri FontaineDate: 2011-12-15 15:53:15
Subject: Re: Command Triggers
Previous:From: Tom LaneDate: 2011-12-15 15:30:13
Subject: Re: splitting plpython into smaller parts

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