| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Streaming replication status |
| Date: | 2010-01-10 20:10:29 |
| Message-ID: | 4B4A3435.6070106@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> We need monitoring anywhere we have a max_* parameter. Otherwise we
> won't know how close we are to disaster until we hit the limit and
> things break down. Otherwise we will have to set parameters by trial and
> error, or set them so high they are meaningless.
I agree.
Thing is, though, we have a de-facto max already ... when pgxlog runs
out of disk space. And no monitoring *in postgresql* for that, although
obviously you can use OS monitoring for it.
I'm saying, even for plain PITR, it would be an improvement in
manageablity if the DBA could set a maximum number of checkpoint
segments before replication is abandonded or the master shuts down.
It's something we've been missing.
--Josh Berkus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Rasheed | 2010-01-10 20:29:06 | Re: Re: CVS HEAD: Error accessing system column from plpgsql trigger function |
| Previous Message | Andrew Dunstan | 2010-01-10 19:58:39 | Re: Feature patch 1 for plperl [PATCH] |