Re: Assert failure when rechecking an exclusion constraint

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, Jeff Davis <pgsql(at)j-davis(dot)com>
Subject: Re: Assert failure when rechecking an exclusion constraint
Date: 2011-06-05 15:51:48
Message-ID: 18094.1307289108@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Noah Misch <noah(at)leadboat(dot)com> writes:
> On Sat, Jun 04, 2011 at 05:49:31PM -0400, Tom Lane wrote:
>> So in short, I'm thinking move lines 1760-1772 (in HEAD) of index.c to
>> the end of index_build(), then insert a ResetReindexProcessing() call in
>> front of them; or maybe only do ResetReindexProcessing there if we
>> actually do call IndexCheckExclusion.

> Sounds reasonable. Need to remove the index from pendingReindexedIndexes, not
> just call ResetReindexProcessing().

[ looks again... ] Uh, right. I was thinking that the pending list was
just "pending" and not "in progress" indexes. I wonder if we should
rejigger things so that that's actually true, ie, remove an index's OID
from the pending list when we mark it as the current one?

> Also, wouldn't that specific construction
> make the catalog updates fail due to running in the table owner's security
> context?

AFAIR there's no security checks happening below this level.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Kupershmidt 2011-06-05 17:06:17 Re: Review: psql include file using relative path
Previous Message Cyan Ogilvie 2011-06-05 15:26:35 WIP: AuthenticationMD5 protocol documentation clarification