| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 18:10:00 |
| Message-ID: | CAM3SWZQsh=uDmyRW4NzYqU_kv8qAsvCYpJuuYSuikfuJbLANQQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
On Fri, May 8, 2015 at 11:06 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2015-05-08 20:37:15 +0300, Heikki Linnakangas wrote:
>> Why does INSERT ON CONFLICT pay attention to indcheckxmin? Uniqueness check
>> only cares about the most recent committed version of the tuple, and the
>> index good for that use immediately. If there was a problem there, the
>> uniqueness check in a normal insert have the same problem.
>
> Yea, that's a good angle to view this from. That'd not be the case, I
> think, if we'd allow this to be used on system relations. But since
> neither creating an index on system relations, nor using INSERT ON
> CONFLICT on them is supported...
+1. I knew we should have done this before commit.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-05-08 18:14:45 | Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 |
| Previous Message | Andres Freund | 2015-05-08 18:06:36 | Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-05-08 18:14:06 | Re: deparsing utility commands |
| Previous Message | Andres Freund | 2015-05-08 18:06:36 | Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 |