Re: Support UPDATE table SET(*)=...

Поиск
Список
Период
Сортировка
Искать
От
Peter Geoghegan
Тема
Re: Support UPDATE table SET(*)=...
Дата
Msg-id
CAM3SWZRCAsFo4d4v6NYwOEHXXQj4teqTf-ft9mUBjmzpP6uMYg@mail.gmail.com
Ответ на
Список
Дерево обсуждения
Support UPDATE table SET(*)=... Atri Sharma <atri.jiit@gmail.com>
Re: Support UPDATE table SET(*)=... Marko Tiikkaja <marko@joh.to>
Re: Support UPDATE table SET(*)=... Tom Lane <tgl@sss.pgh.pa.us>
Re: Support UPDATE table SET(*)=... Michael Paquier <michael.paquier@gmail.com>
Re: Support UPDATE table SET(*)=... Atri Sharma <atri.jiit@gmail.com>
Re: Support UPDATE table SET(*)=... Michael Paquier <michael.paquier@gmail.com>
Re: Support UPDATE table SET(*)=... Atri Sharma <atri.jiit@gmail.com>
Re: Support UPDATE table SET(*)=... Tom Lane <tgl@sss.pgh.pa.us>
Re: Support UPDATE table SET(*)=... Alvaro Herrera <alvherre@2ndquadrant.com>
Re: Support UPDATE table SET(*)=... Jim Nasby <Jim.Nasby@BlueTreble.com>
Re: Support UPDATE table SET(*)=... Tom Lane <tgl@sss.pgh.pa.us>
Re: Support UPDATE table SET(*)=... Peter Geoghegan <pg@heroku.com>
Re: Support UPDATE table SET(*)=... Tom Lane <tgl@sss.pgh.pa.us>
Re: Support UPDATE table SET(*)=... Peter Geoghegan <pg@heroku.com>
Re: Support UPDATE table SET(*)=... Andrew Gierth <andrew@tao11.riddles.org.uk>
Re: Support UPDATE table SET(*)=... Tom Lane <tgl@sss.pgh.pa.us>
Re: Support UPDATE table SET(*)=... Andrew Gierth <andrew@tao11.riddles.org.uk>
Re: Support UPDATE table SET(*)=... Tom Lane <tgl@sss.pgh.pa.us>
Re: Support UPDATE table SET(*)=... Andrew Gierth <andrew@tao11.riddles.org.uk>
Re: Support UPDATE table SET(*)=... Alvaro Herrera <alvherre@2ndquadrant.com>
Re: Support UPDATE table SET(*)=... Tom Lane <tgl@sss.pgh.pa.us>
Re: Support UPDATE table SET(*)=... Andrew Gierth <andrew@tao11.riddles.org.uk>
Re: Support UPDATE table SET(*)=... Marti Raudsepp <marti@juffo.org>
Re: Support UPDATE table SET(*)=... Atri Sharma <atri.jiit@gmail.com>
Re: Support UPDATE table SET(*)=... Merlin Moncure <mmoncure@gmail.com>
Re: Support UPDATE table SET(*)=... Tom Lane <tgl@sss.pgh.pa.us>
Re: Support UPDATE table SET(*)=... Marko Tiikkaja <marko@joh.to>
Re: Support UPDATE table SET(*)=... Merlin Moncure <mmoncure@gmail.com>
Re: Support UPDATE table SET(*)=... Tom Lane <tgl@sss.pgh.pa.us>
Re: Support UPDATE table SET(*)=... Merlin Moncure <mmoncure@gmail.com>
Re: Support UPDATE table SET(*)=... Marko Tiikkaja <marko@joh.to>
Re: Support UPDATE table SET(*)=... Tom Lane <tgl@sss.pgh.pa.us>
Re: Support UPDATE table SET(*)=... Marti Raudsepp <marti@juffo.org>
Re: Support UPDATE table SET(*)=... Merlin Moncure <mmoncure@gmail.com>
Re: Support UPDATE table SET(*)=... Tom Lane <tgl@sss.pgh.pa.us>
Re: Support UPDATE table SET(*)=... Merlin Moncure <mmoncure@gmail.com>
Re: Support UPDATE table SET(*)=... Merlin Moncure <mmoncure@gmail.com>
Re: Support UPDATE table SET(*)=... Atri Sharma <atri.jiit@gmail.com>
Re: Support UPDATE table SET(*)=... Atri Sharma <atri.jiit@gmail.com>
On Tue, Apr 7, 2015 at 12:01 PM, Peter Geoghegan  wrote:
> I still don't like the idea of
> supporting this, though. I'm not aware of any other system allowing
> something like this for either MERGE or a non-standard UPSERT.

That includes MySQL, BTW. Only their REPLACE statement (which is a
disaster for various reasons) can do something like this. Their INSERT
... ON DUPLICATE KEY UPDATE statement (which is roughly comparable to
the proposed UPSERT patch) cannot update the entire row using a terse
expression that references a row excluded from insertion (following
the implementation taking the UPDATE path).

-- 
Peter Geoghegan


В списке pgsql-hackers по дате отправления
От: Peter Geoghegan
Дата:
От: Tom Lane
Дата:
FAQ