Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity.

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity.
Date: 2016-03-10 21:51:03
Message-ID: CAFj8pRAjRzmdi6_NBfkQgZefbJ2s+i8g=us79GzCy9YQ=puLmg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

2016-03-10 22:24 GMT+01:00 Robert Haas <robertmhaas(at)gmail(dot)com>:

>
> rhaas=# select query, state, wait_event, wait_event_type from
> pg_stat_activity;
> query
> | state | wait_event | wait_event_type
>
> -------------------------------------------------------------------------+--------+---------------+-----------------
> select query, state, wait_event, wait_event_type from
> pg_stat_activity; | active | |
> select * from foo for update;
> | active | transactionid | Lock
> (2 rows)
>
> ...which looks right to me.
>
> > session two:
> > rollback; begin; select * from foo where a = 10 for update;
> > session two is waiting again
>
> I don't see how you can do this here - the session is blocked.
>
> There could well be a bug here, but I need a little more help to find it.
>

Maybe it be clear from attached text file

Regards

>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>

Attachment Content-Type Size
err.txt text/plain 3.6 KB

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2016-03-10 22:05:00 Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity.
Previous Message Robert Haas 2016-03-10 21:24:55 Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity.

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-03-10 22:05:00 Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity.
Previous Message Regina Obe 2016-03-10 21:29:39 Re: Is there a way around function search_path killing SQL function inlining? - and backup / restore issue