| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE |
| Date: | 2013-09-15 14:52:23 |
| Message-ID: | 1379256743.22934.YahooMailNeo@web162902.mail.bf1.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> There is no reason to call CheckForSerializableConflictIn() with
> the additional locks held either. After all, "For a heap insert,
> we only need to check for table-level SSI locks".
You're only talking about not covering that call with a *new*
LWLock, right? We put some effort into making sure that such calls
were only inside of LWLocks which were needed for correctness.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Tiikkaja | 2013-09-15 15:03:10 | Re: Where to load modules from? |
| Previous Message | Peter Eisentraut | 2013-09-15 14:51:01 | Re: Where to load modules from? |