From: | Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: system views for walsender activity |
Date: | 2010-12-28 13:14:19 |
Message-ID: | AANLkTi=tKMj_z8tktOW1k-HxFMwy6-ryecENyeQEjuwa@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Dec 28, 2010 at 21:46, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> Unfortunately, 2 also requires initdb because pg_stat_activity will
>> use LEFT JOIN instead of normal JOIN not to hide rows with databaseid = 0.
>> All of them are items for 9.1.
>
> Did this one end up on the floor?
>
> We definitely need the very basic level for 9.1, and we can always
> improve on it later :-) Do you want to keep working on it, or do you
> want me to pick it up?
OK, I'll work for it.
> I'm not sure it makes much sense to add walsenders to pg_stat_activity
> - a lot of the fields would no longer make any sense (statement start?
> query start?) - I think we're better off with a separate view for
> pg_stat_walsender. It would then only need the columns for procpid,
> usesysid, usename, client_addr, client_port, and the WALsender
> specific fields.
+1 for the separate view. "backend_start" (or replication_start?)
might be also reasonable.
--
Itagaki Takahiro
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2010-12-28 13:14:46 | Re: "writable CTEs" |
Previous Message | Magnus Hagander | 2010-12-28 12:49:06 | Function for dealing with xlog data |