Re: Re: [COMMITTERS] pgsql: Add support for INSERT ... ON CONFLICT DO NOTHING/UPDATE.

Поиск
Список
Период
Сортировка
От Simon Riggs
Тема Re: Re: [COMMITTERS] pgsql: Add support for INSERT ... ON CONFLICT DO NOTHING/UPDATE.
Дата
Msg-id CANP8+jLSvqqd_TrusWr=MiPxMf6c1a9sw7CxzX=rCZJMwmw_Og@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Re: [COMMITTERS] pgsql: Add support for INSERT ... ON CONFLICT DO NOTHING/UPDATE.  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Список pgsql-hackers
Дерево обсуждения
On 27 May 2015 at 15:06, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
Simon Riggs wrote:

> What I think should happen is that the command tag should vary according to
> whether an INSERT or an UPDATE was performed, so we get a visible
> difference without any new tags.

The problem with doing that is that the same command might have updated
some tuples and inserted others.  Also, we build the tag before the
command is executed.

Hmm,  I assumed the various anomalies meant that it was a single row only command...

Anybody know where the various anomalies are documented? e.g. how if an insert has been committed that we can't yet see whether we are allowed to update that using same rules as update. 

--
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Triggers on transaction?
Следующее
От: Stephen Frost
Дата:
Сообщение: Re: [COMMITTERS] pgsql: Add pg_audit, an auditing extension