Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE

Поиск
Список
Период
Сортировка
От Greg Stark
Тема Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE
Дата
Msg-id CAM-w4HOkVWDE_6907nL-HTHaZR2tze57WLSF3Vy8CwHhaGQRZg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE  (Peter Geoghegan <pg@heroku.com>)
Ответы Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE  (Peter Geoghegan <pg@heroku.com>)
Список pgsql-hackers
On Sat, Jan 11, 2014 at 12:51 AM, Peter Geoghegan <pg@heroku.com> wrote:
> On Fri, Jan 10, 2014 at 4:09 PM, Jim Nasby <jim@nasby.net> wrote:
>> Well, the usual example for exclusion constraints is resource scheduling
>> (ie: scheduling what room a class will be held in). In that context is it
>> hard to believe that you might want to MERGE a set of new classroom
>> assignments in?
>
> So you schedule a class that clashes with 3 other classes, and you
> want to update all 3 rows/classes with details from your one row
> proposed for insertion?


Well, perhaps you want to mark the events as conflicting with your new event?

-- 
greg



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

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: [PATCH] Store Extension Options
Следующее
От: Amit Kapila
Дата:
Сообщение: Re: Performance Improvement by reducing WAL for Update Operation