| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Christian Kruse <christian(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Subject: | Re: Patch: show xid and xmin in pg_stat_activity and pg_stat_replication |
| Date: | 2014-02-18 21:02:44 |
| Message-ID: | 20140218210244.GB28858@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2014-02-17 10:44:41 +0100, Christian Kruse wrote:
> This is true for now. But one of the purposes of using
> LocalPgBackendStatus instead of PgBackendStatus was to be able to add
> more fields like this in future. And thus we might need to change this
> in future, so why not do it now?
I don't think that argument is particularly valid. All (?) the other
functions just return just one value, so they won't ever have the need
to return more.
Not really sure which way is better.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-02-18 21:05:04 | Re: Do you know the reason for increased max latency due to xlog scaling? |
| Previous Message | Heikki Linnakangas | 2014-02-18 21:01:08 | Re: Do you know the reason for increased max latency due to xlog scaling? |