| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: system views for walsender activity |
| Date: | 2011-01-09 14:53:28 |
| Message-ID: | 1294584808.1712.597.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, 2011-01-09 at 12:52 +0100, Magnus Hagander wrote:
> One thing I noticed is that it gives an interesting property to my
> patch for streaming base backups - they now show up in
> pg_stat_replication, with a streaming location of 0/0.
>
> If the view is named pg_stat_replication, we probably want to filter
> that out somehow. But then, do we want a separate view listing the
> walsenders that are busy sending base backups?
>
> For that matter, do we want an indication that separates a walsender
> not sending data from one sending that happens to be at location 0/0?
> Most will leave 0/0 really quickly, but a walsender can be idle (not
> received a command yet), or it can be running IDENTIFY_SYSTEM for
> example.
I think we need a status enum. ('BACKUP', 'CATCHUP', 'STREAM') for the 3
phases of replication.
--
Simon Riggs http://www.2ndQuadrant.com/books/
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2011-01-09 14:57:14 | Re: SSI patch(es) |
| Previous Message | Magnus Hagander | 2011-01-09 14:41:01 | pgsql: Properly install gram.h on MSVC builds |