Re: IDLE in transaction introspection
| От | Simon Riggs |
|---|---|
| Тема | Re: IDLE in transaction introspection |
| Дата | |
| Msg-id | CA+U5nMJc5jkFp3b6MA2hUHbg-D5Lmd3PTE-fc-8NWzYK0_g5GA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: IDLE in transaction introspection (Robert Haas <robertmhaas@gmail.com>) |
| Ответы |
Re: IDLE in transaction introspection
Re: IDLE in transaction introspection |
| Список | pgsql-hackers |
On Mon, Oct 31, 2011 at 10:13 PM, Robert Haas <robertmhaas@gmail.com> wrote: > On Mon, Oct 31, 2011 at 5:45 PM, Magnus Hagander <magnus@hagander.net> wrote: >> Actually, for the future, it might be useful to have a "state" column, >> that holds the idle/in transaction/running status, instead of the >> tools having to parse the query text to get that information... > > +1 for doing it this way. Splitting "current_query" into "query" and > "state" would be more elegant and easier to use all around. Why not leave it exactly as it is, and add a previous_query column? That gives you exactly what you need without breaking anything. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: