Re: IDLE in transaction introspection

From: Marti Raudsepp <marti(at)juffo(dot)org>
To: Scott Mead <scottm(at)openscg(dot)com>
Cc: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, "Andrew Dunstan *EXTERN*" <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 11:39:15
Message-ID: CABRT9RALaKEwvoHXRrnqoCcXJN6uFqockkFt5KFkachA8sNBTQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 2, 2011 at 20:18, Scott Mead <scottm(at)openscg(dot)com> wrote:
>    State will display <RUNNING>, <IDLE>, <IDLE> in transaction, etc...

While we're already breaking everything, we could remove the "waiting"
column and use a state with value 'waiting' instead.

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

Or we could return single-character mnemonics like some pg_catalog
tables do, and substitute them in the view.

Regards,
Marti

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gabriele Bartolini 2011-11-04 12:48:02 [PATCH] Support for foreign keys with arrays
Previous Message Noah Misch 2011-11-04 11:34:33 Re: psql expanded auto