Re: [COMMITTERS] pgsql: Allow Pin/UnpinBuffer to operate in a lockfree manner.

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Allow Pin/UnpinBuffer to operate in a lockfree manner.
Date: 2016-04-14 00:04:12
Message-ID: 20160414000412.7b7yocwptunnbptt@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 2016-04-13 11:20:19 -0700, Andres Freund wrote:
> On 2016-04-13 14:16:15 -0400, Tom Lane wrote:
> > Good point, it would be absolutely duplicative. What I'd suggest,
> > actually, is that we convert this to the same info as what elog
> > provides (file+line+function name).
>
> Heh, I was wondering the same aftering sending the last email. Will do
> that then.

Pushed. Let's see what pademelon says...

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2016-04-14 00:09:46 Re: [COMMITTERS] pgsql: Allow Pin/UnpinBuffer to operate in a lockfree manner.
Previous Message Andres Freund 2016-04-14 00:02:57 pgsql: Make init_spin_delay() C89 compliant and change stuck spinlock r

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-04-14 00:06:02 Re: \crosstabview fixes
Previous Message David G. Johnston 2016-04-13 23:57:33 Re: SET ROLE and reserved roles