Re: different transaction handling between postgresql and
От | Shridhar Daithankar |
---|---|
Тема | Re: different transaction handling between postgresql and |
Дата | |
Msg-id | 3F12C5D9.16043.643FA2@localhost обсуждение исходный текст |
Ответ на | Re: different transaction handling between postgresql and (Mike Mascari <mascarm@mascari.com>) |
Ответы |
Re: different transaction handling between postgresql and
|
Список | pgsql-general |
On 14 Jul 2003 at 5:18, Mike Mascari wrote: > I agree. However a common scenario that has appeared on these lists is > a request for an atomic 'CREATE IF NOT EXISTS, ELSE REPLACE' without > race conditions. Because Oracle doesn't rollback the transaction, it > is implementable in SQL. For PostgreSQL, you either need to use > various locking techniques which reduces concurrency or be prepared to > resubmit the entire transaction. Savepoints and/or nested transactions > may alleviate the situation in the future, however. Recognising the need of such, SQL standard has been extended to accommodate a merge command which is create if not exists else update types. Correct me if I am wrong.. BTW, what's wrong with select for update in such scenario? Bye Shridhar -- Feel free to contact me (flames about my english and the useless of thisdriver will be redirected to /dev/null, oh no, it's full...).(Michael Beck, describing the PC-speaker sound device)
В списке pgsql-general по дате отправления: