| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: new "row-level lock" error messages |
| Date: | 2013-07-17 18:43:35 |
| Message-ID: | 20130717184335.GG4165@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut wrote:
> In general, I find these new wordings to be a loss of clarity. There is
> no indication on the SELECT man page or in the documentation index what
> a "row-level lock" is at all.
>
> I would suggest that these changes be undone, except that the old
> "SELECT FOR ..." be replaced by a dynamic string that reverse-parses the
> LockingClause to provide the actual clause that was used.
Hmm, that's an idea. If there are no objections, I'll get this fixed.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2013-07-17 18:47:46 | Re: Listen/notify across clusters |
| Previous Message | Josh Berkus | 2013-07-17 18:08:59 | Re: Listen/notify across clusters |