From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: column name of pg_stat_replication.backend_start |
Date: | 2012-04-14 13:05:50 |
Message-ID: | CABUevExWB1CE+qf7zbwkd0TC_7nRWzOG-6P1EetxocV72isFiQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Apr 14, 2012 at 14:22, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Sat, Apr 14, 2012 at 8:00 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>> The column name of pg_stat_replication.backend_start is confusing because
>> it's not the time when *backend* was started at all. We should rename it to
>> "walsender_start" or "replication_start"?
>
> walsenders are backends, of course. I think that any clarity we'd get
> from renaming this would be not worth the loss of backward
> compatibility or the inconsistency with pg_stat_activity.
There was a suggestion the other day I think from Bruce to rename it
to session_start in pg_stat_activity. If we do that, we should
probably rename it in pg_stat_replication *as well*, of course...
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2012-04-14 13:34:56 | Re: Memory usage during sorting |
Previous Message | Greg Stark | 2012-04-14 12:32:04 | Re: Memory usage during sorting |