[pgpool-general: 7394] Re: non-default tablespaces

Murat K srvrmurat at gmail.com
Sat Jan 16 17:29:52 JST 2021

Dear Tatsuo,

I am implementing example setup on pgpool website. Nothing different from
setup. It runs successfully. In case of failover, standby follows the new
primary db and syncronizes. What I see is /var/lib/pgsql/13/data is moved
to .../data.old.

Then I created two non-default tablespaces in /u01/xxx and /u01/yyy. Tried
the failover but it is not working. It looks follow_primary.sh is not
working as before. I could not find any clue. Shall I move non-default
tablespaces to xxx.old, yyy.old at beginning of follow_primary.sh? What is
the proper way of working with non-defult tablespaces?


On Fri, Jan 15, 2021 at 11:43 AM Tatsuo Ishii <ishii at sraoss.co.jp> wrote:

> > Dear All,
> >
> > My configuration is pgpool 4.2.1, postgresql-13 and centos7. I have
> > non-default tablespaces. It looks in case of recovery and failover it is
> > not working as I anticipated. As far as I see pgpool moves var directory
> to
> > var.old but for non-default tablespace directories it does not behave
> like
> > that. What is the proper way of working with non-default tablespaces?
> Can you elaborate more? How exactly Pgpool-II does not work as you
> expected?  Since for recovery and failover you need to provide scripts
> to perform actual recovery and failover, without sharing those scripts
> I cannot say anything about what's wrong.
> Also I don't understand "pgpool moves var directory to var.old"
> because Pgpool-II does not have code that does that.
> Best regards,
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20210116/9f5c0f13/attachment.htm>

More information about the pgpool-general mailing list