| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| 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:53:38 |
| Message-ID: | 13525.1395161618@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> 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?
It's pretty lousy from a readability standpoint, even in English;
I shudder to think what it might come out as after translation.
I think the enum idea you floated is probably worth doing. It's
certainly no more complex than passing a string, no?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Claudio Freire | 2014-03-18 16:53:53 | Re: Planner hints in Postgresql |
| Previous Message | Alvaro Herrera | 2014-03-18 16:43:25 | Re: Patch: show relation and tuple infos of a lock to acquire |