> 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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
