2011/8/22 Toshihiro Kitagawa <kitag...@sraoss.co.jp>: >> OK, I think I found : >> >> In my config file : >> >> # system DB info >> system_db_hostname = 'fpg01' >> system_db_port = 5432 >> system_db_dbname = 'pgpool' >> system_db_schema = 'pgpool_catalog' >> system_db_user = 'pgpool' >> system_db_password = 'password' >> >> but the pgpool_* scripts are stored in the public schema. I will try >> with the scripts in the pgpool_catalog schema. > > No, system DB is used in parallel query mode or query cache. > So it is unrelated. The installation of the functions is required on > all backends, not system DB.
OK All the backend have the functions since the streaming and replication are working. I have the same error, the functions are in public and pgpool_catalog : 2011-08-22 10:00:55 LOG: pid 10849: find_primary_node: pgpool_walrecrunning does not exist On master : 10:36 pgsql@fpg01:~$ psql -U pgpool pgpool psql (9.0.4) Saisissez « help » pour l'aide. pgpool=> select pgpool_walrecrunning(); pgpool_walrecrunning ---------------------- f (1 ligne) On slave 1 : pgpool=> select pgpool_walrecrunning(); pgpool_walrecrunning ---------------------- t (1 ligne) On slave 2 : pgpool=> select pgpool_walrecrunning(); pgpool_walrecrunning ---------------------- t (1 ligne) f for false and t for true ? So why doesn't pgpool found my master node? Olivier > -- > Toshihiro Kitagawa > SRA OSS, Inc. Japan > > _______________________________________________ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general