From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: LockDatabaseObject vs. LockSharedObject |
Date: | 2010-08-15 21:15:58 |
Message-ID: | 5494.1281906958@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Sun, Aug 15, 2010 at 3:22 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I'm not sure that we have any non-relation objects that are both complex
>> enough and changeable enough for there to be an observable bug here,
>> but it seems like a risk factor going forward. It seems to me both safe
>> and reasonable to add an AcceptInvalidationMessages call in HEAD.
> My "comment refactoring" patch (already posted to the list) makes this
> change among others.
OK. I haven't read that yet, and wasn't intending to until you respond
to Alvaro's suggestions. But it might be worth committing this change
separately, since it seems to have merit independently of whether we
make those other changes.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-08-15 21:17:50 | Re: DropRelFileNodeBuffers API change (was Re: [BUGS] BUG #5599: Vacuum fails due to index corruption issues) |
Previous Message | Robert Haas | 2010-08-15 21:10:00 | Re: LockDatabaseObject vs. LockSharedObject |