| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Christian Kruse <christian(at)2ndquadrant(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Patch: show relation and tuple infos of a lock to acquire |
| Date: | 2014-03-18 16:43:25 |
| Message-ID: | 20140318164325.GV6899@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane escribió:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > Well, if we're back to one version of the message, and I'm glad we
> > are, can we go back to saying:
>
> > CONTEXT: while updating tuple (0,2) in relation "public"."foo" of
> > database "postgres"
>
> If I end up being the one who commits this, it's going to say
>
> while updating tuple (0,2) in table "foo"
>
> Not more, and not less.
Please see my reply to Robert. My proposal (in form of a patch) is
while operating on tuple (0,2) in table "foo": updating tuple
Would this work for you?
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-03-18 16:53:38 | Re: Patch: show relation and tuple infos of a lock to acquire |
| Previous Message | Tom Lane | 2014-03-18 16:38:41 | Re: Patch: show relation and tuple infos of a lock to acquire |