Re: Patch: show relation and tuple infos of a lock to acquire - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Patch: show relation and tuple infos of a lock to acquire
Date
Msg-id 20140318194927.GZ6899@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: Patch: show relation and tuple infos of a lock to acquire  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Patch: show relation and tuple infos of a lock to acquire  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
Tom Lane escribió:
> Alvaro Herrera <alvherre@2ndquadrant.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.

Well, the same thing actually.  I didn't think it was too bad.

> I think the enum idea you floated is probably worth doing.  It's
> certainly no more complex than passing a string, no?

Okay, done that way, attached.  I think this one solves all concerns
there were.

--
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: plpgsql.warn_shadow
Next
From: Pavel Stehule
Date:
Subject: Re: plpgsql.warn_shadow