| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, 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:07:38 |
| Message-ID: | 18691.1431112058@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
Peter Geoghegan <pg(at)heroku(dot)com> writes:
> On Fri, May 8, 2015 at 11:59 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Ooops. But shouldn't that have failed 100% of the time in a CCA build?
>> Or is the candidates list fairly noncritical?
> The candidates list is absolutely critical.
Oh, I was confusing CCA with RELCACHE_FORCE_RELEASE, which does something
a bit different. I wonder whether we should get rid of that symbol and
just drive the test in RelationClose off CLOBBER_CACHE_ALWAYS.
(Ditto for CATCACHE_FORCE_RELEASE.) Or maybe make CLOBBER_CACHE_ALWAYS
#define the other two symbols.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2015-05-08 19:09:47 | Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 |
| Previous Message | Stephen Frost | 2015-05-08 19:06:50 | Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2015-05-08 19:07:42 | pgsql: At promotion, archive last segment from old timeline with .parti |
| Previous Message | Stephen Frost | 2015-05-08 19:06:50 | Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 |