Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0
| От | Peter Geoghegan |
|---|---|
| Тема | Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 |
| Дата | |
| Msg-id | CAM3SWZQsh=uDmyRW4NzYqU_kv8qAsvCYpJuuYSuikfuJbLANQQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 (Andres Freund <andres@anarazel.de>) |
| Ответы |
Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0
|
| Список | pgsql-hackers |
On Fri, May 8, 2015 at 11:06 AM, Andres Freund <andres@anarazel.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
В списке pgsql-hackers по дате отправления: