Horton

Re: foreign key locks, 2nd attempt

Jeroen Vermeulen <jtv@xs4all.nl>

View thread
From: Jeroen Vermeulen <jtv@xs4all.nl>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2011-11-06T07:28:52Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Try to avoid running with a full fsync request queue.

On 2011-11-04 01:12, Alvaro Herrera wrote:

> I would like some opinions on the ideas on this patch, and on the patch
> itself.  If someone wants more discussion on implementation details of
> each part of the patch, I'm happy to provide a textual description --
> please just ask.

Jumping in a bit late here, but thanks for working on this: it looks 
like it could solve some annoying problems for us.

I do find myself idly wondering if those problems couldn't be made to go 
away more simply given some kind of “I will never ever update this key” 
constraint.  I'm having trouble picturing the possible lock interactions 
as it is.  :-)


Jeroen