Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Geoghegan <pg(at)heroku(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0
Date: 2015-05-08 19:09:57
Message-ID: 20150508190957.GW12950@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

On 2015-05-08 14:59:22 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > I think Peter (on IM) just found a more likely explanation than mine.
> > index_close(idxRel, NoLock);
> > heap_close(relation, NoLock);
> > candidates = lappend_oid(candidates, idxForm->indexrelid);
> > ...
> > Yes. idxForm points into idxRel->rd_index.
>
> Ooops. But shouldn't that have failed 100% of the time in a CCA build?
> Or is the candidates list fairly noncritical?

Afaics RELCACHE_FORCE_RELEASE is independent of CCA (should we change
that?). So this probably a bug, just not a relevant bug. I can't see
how it'd take affect in this case.

Greetings,

Andres Freund

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2015-05-08 19:13:04 Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0
Previous Message Stephen Frost 2015-05-08 19:09:47 Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-05-08 19:13:04 Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0
Previous Message Stephen Frost 2015-05-08 19:09:47 Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0