Re: advisory locks and permissions
От | Bruce Momjian |
---|---|
Тема | Re: advisory locks and permissions |
Дата | |
Msg-id | 200609221858.k8MIwia11643@momjian.us обсуждение исходный текст |
Ответ на | Re: advisory locks and permissions (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: advisory locks and permissions
|
Список | pgsql-hackers |
Tom Lane wrote: > "Merlin Moncure" <mmoncure@gmail.com> writes: > > advisory locks still show up as 'userlock' in the pg_locks view. does > > this matter? > > I'm disinclined to change that, because it would probably break existing > client-side code for little gain. I think clarity suggests we should make the heading match the feature, i.e call it "advisory" rather than "userlock". We changed the API, I don't see why keeping the heading makes sense. I think we should leave it unprotected unless we find out that there are unique security problems with advisory locks. -- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
В списке pgsql-hackers по дате отправления: