Re: xlog.c: WALInsertLock vs. WALWriteLock

From: David Fetter <david(at)fetter(dot)org>
To: fazool mein <fazoolmein(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: xlog.c: WALInsertLock vs. WALWriteLock
Date: 2010-10-23 20:17:43
Message-ID: 20101023201743.GB20820@fetter.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 22, 2010 at 12:08:54PM -0700, fazool mein wrote:
> Hello guys,
>
> I'm writing a function that will read data from the buffer in xlog
> (i.e. from XLogCtl->pages and XLogCtl->xlblocks). I want to make
> sure that I am doing it correctly.

Got an example of what the function might look like?

> For reading from the buffer, do I need to lock WALInsertLock or
> WALWriteLock? Also, can you explain a bit the usage of 'LW_SHARED'.
> Can we use it for read purposes?

Help me understand. Do you foresee some kind of concurrency issue,
and if so, what?

Cheers,
David.
>
> Thanks a lot.

--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Boxuan Zhai 2010-10-23 20:30:10 Re: ask for review of MERGE
Previous Message A.M. 2010-10-23 19:47:01 create c function with void argument bug?