| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, "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 23:17:22 |
| Message-ID: | 15170.1457651842@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Or ... maybe this is intentional behavior? Now that I think about it,
> doesn't each backend cache this info the first time its transaction
> reads the data?
Your view of pg_stat_activity is supposed to hold still within a
transaction, yes. Otherwise it'd be really painful to do any complicated
joins. I think there may be a function to explicitly flush the cache,
if you really need to see intratransaction changes.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-03-10 23:19:15 | Re: pgsql: Don't vacuum all-frozen pages. |
| Previous Message | Robert Haas | 2016-03-10 22:08:18 | Re: [COMMITTERS] pgsql: Provide much better wait information in pg_stat_activity. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2016-03-10 23:23:56 | Re: checkpointer continuous flushing - V18 |
| Previous Message | Fabien COELHO | 2016-03-10 23:15:15 | Re: checkpointer continuous flushing - V18 |