Re: IDLE in transaction introspection

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Marti Raudsepp <marti(at)juffo(dot)org>
Cc: Scott Mead <scottm(at)openscg(dot)com>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, "Andrew Dunstan *EXTERN*" <andrew(at)dunslane(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: IDLE in transaction introspection
Date: 2011-11-04 13:42:02
Message-ID: 5843.1320414122@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Marti Raudsepp <marti(at)juffo(dot)org> writes:
> While we're already breaking everything, we could remove the "waiting"
> column and use a state with value 'waiting' instead.

-1 ... I think it's useful to see the underlying state as well as the
waiting flag. Also, this would represent breakage of part of the API
that doesn't need to be broken.

> Also, returning these as text seems a little lame. Should there be an
> enum type for that?

Perhaps, but we don't really use enum types in any other system views,
so inventing one here would be out of character.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-11-04 13:45:06 Re: Show sequences owned by
Previous Message Magnus Hagander 2011-11-04 13:34:05 Show statistics target in \d+