Re: column name of pg_stat_replication.backend_start - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: column name of pg_stat_replication.backend_start
Date
Msg-id CAHGQGwFyFVHNJZ3AQ-Tt-Lp9Fu+ARThO6aqHTOtX0T=S+ANmxQ@mail.gmail.com
Whole thread Raw
In response to Re: column name of pg_stat_replication.backend_start  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On Sat, Apr 14, 2012 at 10:05 PM, Magnus Hagander <magnus@hagander.net> wrote:
> On Sat, Apr 14, 2012 at 14:22, Robert Haas <robertmhaas@gmail.com> wrote:
>> On Sat, Apr 14, 2012 at 8:00 AM, Fujii Masao <masao.fujii@gmail.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...

Yep, agreed.

Regards,

--
Fujii Masao


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: missing description initdb manual
Next
From: Robert Haas
Date:
Subject: Re: [COMMITTERS] pgsql: Add new replication mode synchronous_commit = 'write'.