Re: Issue NOTICE for attempt to raise lock level?
| От | Peter Eisentraut |
|---|---|
| Тема | Re: Issue NOTICE for attempt to raise lock level? |
| Дата | |
| Msg-id | Pine.LNX.4.21.0011071919520.1192-100000@peter.localdomain обсуждение исходный текст |
| Ответ на | Issue NOTICE for attempt to raise lock level? (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-hackers |
Tom Lane writes: > To help debug this, I'm planning to add a little bit of code to the > lock manager that detects a request for a lock on an object on which > we already hold a lock of a lower level. What I'm wondering about is > whether to make the report be elog(DEBUG) --- ie, send to postmaster > log only --- or elog(NOTICE), so that users would see it by default. To me this seems to be a little like the much-disputed notice for adding implicit range-table entries: Either it's an error, then you abort, or it's legal, then you leave the user alone and perhaps explain failure scenarios in the documentation. At least until we have something like a user-configurable warning level. elog(DEBUG) might be okay, but only with a positive DebugLvl, IMHO. -- Peter Eisentraut peter_e@gmx.net http://yi.org/peter-e/
В списке pgsql-hackers по дате отправления: