Re: pgsql: Make LockDatabaseObject() AcceptInvalidationMessages().

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Robert Haas <rhaas(at)postgresql(dot)org>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Make LockDatabaseObject() AcceptInvalidationMessages().
Date: 2010-08-25 18:51:03
Message-ID: 23342.1282762263@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, Aug 25, 2010 at 11:46 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> I have a horrible nagging feeling this breaks something.

> Well, the only place it's used at the moment is in the drop-object
> code. Not sure if that might be enough to jog your memory?

Also, it's pretty hard to see how this could break anything that isn't
already broken, because AcceptInvalidationMessages() already happens
in the other cases in that code path.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2010-08-25 19:37:30 pgsql: Catch null pointer returns from PyCObject_AsVoidPtr and
Previous Message Peter Eisentraut 2010-08-25 18:18:41 pgsql: Add missing description of reloftype field