Thanks for answers. On Thu, Sep 29, 2011 at 2:59 PM, Tatsuo Ishii <is...@sraoss.co.jp> wrote:
> > Hello, > > > > > > first, I'm sorry if it is already been asked, but I can not find it. > > > > What is suggestion for vaccum or autovacuum for pgpool configurations. > > I have pgpool configured for streaming replication. > > Should I set autovacuum, or should I start autovacuum manually > periodically? > > > > I see that during online recovery, autovacuum should be disabled... but > > thats for replication mode, > > is it same for streaming replication? > > No. If you are using streaming repliation mode of pgpool-II you don't > need to worry about autovacuum. Just let PostgreSQL automatically > start autovacuum even while online recovery. > > > Should autovacuum be launched through pgpool, or should I connect to > > database directly? > > I'm confused. Autovacuum is always launched by PostgreSQL, it's one of > PostgreSQL's background process and never be launched by user > manually. Maybe you are mixing up autovacuum and VACUUM command? > Sorry, I you'r right, my question was for VACUUM command, not autovacuum. > > > This is normal when trying to start vacuum on slave node? > > > > db1=> VACUUM FULL VERBOSE ANALYZE; > > ERROR: cannot execute VACUUM during recovery > > Yes. Streaming replication slave is running in read-only mode. Thus > you cannot issue any database-write command including VACUUM. Instead > run vacuum on master. The effect of vacuum will be applied to slaves > through streaming replication. > -- > Tatsuo Ishii > SRA OSS, Inc. Japan > English: http://www.sraoss.co.jp/index_en.php > Japanese: http://www.sraoss.co.jp > -- Armin
_______________________________________________ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general