From: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
---|---|
To: | masao(dot)fujii(at)gmail(dot)com |
Cc: | martin(dot)pihlak(at)gmail(dot)com, greg(at)2ndquadrant(dot)com, pgsql-cluster-hackers(at)postgresql(dot)org |
Subject: | Re: Cluster feature: Start/stop archiving at runtime |
Date: | 2010-03-02 08:59:59 |
Message-ID: | 20100302.175959.55510077.t-ishii@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-cluster-hackers |
> On Tue, Mar 2, 2010 at 4:42 PM, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> wrote:
> > My interpretation of this paragraph is, if we set archive_command to
> > empty string, PostgreSQL accumulates all WAL under pg_xlog. i.e. no
> > WAL resuing occurs. Maybe set archive_command to /bin/true is enough
> > for pgpool-II, but it needs to rewrite postgresql.conf by pgpool. That
> > may make users to feel uncomfortable, I'm afraid.
>
> I understood that what is needed here is the capability to start/stop
> archiving without changing any configuration file. Instead of reloading
> the conf file, what API do you want? Controlling archiving via system
> catalog like pg_autovacuum (though it's obsolete) is sufficient?
I prefer to use functions.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2010-03-03 07:19:45 | Expanded information template |
Previous Message | Fujii Masao | 2010-03-02 08:26:45 | Re: Cluster feature: Start/stop archiving at runtime |