Tue Apr 7 00:12:57 PDT 2009
- Previous message: [Slony1-general] replication stalled.
- Next message: [Slony1-general] Slony querries.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Madan Thapa wrote: > >> >> >> I have installed postgresql using yum. >> >> >> -bash-3.2# rpm -qa | grep postgres >> postgresql-libs-8.3.5-1PGDG.rhel5 >> postgresql-8.3.5-1PGDG.rhel5 >> postgresql-server-8.3.5-1PGDG.rhel5 >> compat-postgresql-libs-4-1PGDG.rhel5 >> >> >> >> -bash-3.2# ps faux | egrep 'pgsql|postgres' >> postgres 23733 0.0 0.7 40716 4108 ? S Jan29 0:02 >> /usr/bin/postmaster -p 5432 -D /var/lib/pgsql/data >> postgres 23758 0.0 0.1 12040 888 ? Ss Jan29 0:00 \_ >> postgres: logger process >> postgres 23761 0.0 0.2 40716 1228 ? Ss Jan29 0:00 \_ >> postgres: writer process >> postgres 23763 0.0 0.1 40716 1028 ? Ss Jan29 0:00 \_ >> postgres: wal writer process >> postgres 23764 0.0 0.2 40848 1136 ? Ss Jan29 0:00 \_ >> postgres: autovacuum launcher process >> postgres 23765 0.0 0.1 12036 920 ? Ss Jan29 0:00 \_ >> postgres: stats collector process >> root 11393 0.0 0.1 2992 704 pts/0 S+ 05:44 0:00 \_ >> egrep pgsql|postgres >> -bash-3.2# >> >> >> >> >> Now to install slony what would be pg_config path ? >> >> Docs sasy: >> *Normally,* it ought to be sufficient to run configure >> --with-pgconfigdir=/some/path/somewhere, where /some/path/somewhere is >> the >> place where the PostgreSQL program *pg_config* is located. From >> *pg_config >> *, the configure script can determine the various locations where >> PostgreSQL components are found, which indicates where the essential >> components of Slony-I must be installed. >> >> >> -bash-3.2# locate pg_config >> locate: can not open `/var/lib/mlocate/mlocate.db': No such file or >> directory >> -bash-3.2# updatedb >> -bash-3.2# locate pg_config >> -bash-3.2# ls /var/lib/pgsql/data/ >> base pg_clog pg_ident.conf pg_multixact pg_tblspc PG_VERSION >> postgresql.conf postmaster.pid >> global pg_hba.conf pg_log pg_subtrans pg_twophase pg_xlog >> postmaster.opts >> -bash-3.2# >> >> >> >> -bash-3.2# find / -name pg_config >> -bash-3.2# >> -bash-3.2# >> >> >> >> >> >> Path of some important binaries on my system are >> ################################################# >> /usr/bin/psql >> /usr/bin/createdb >> /usr/bin/createlang >> /usr/bin/createuser >> /usr/bin/pg_dump >> >> >> >> >> Please advise. >> >> >> Thanks >> >> > ========================> > > *yum install slony1 did it* > > > -bash-3.2# yum install slony1 > pgdg83 100% |=========================| 1.9 kB 00:00 > rpmforge 100% |=========================| 1.1 kB 00:00 > base 100% |=========================| 1.1 kB 00:00 > updates 100% |=========================| 951 B 00:00 > addons 100% |=========================| 951 B 00:00 > extras 100% |=========================| 1.1 kB 00:00 > Setting up Install Process > Parsing package install arguments > Resolving Dependencies > --> Running transaction check > ---> Package slony1.i386 0:1.2.15-3.rhel5 set to be updated > --> Processing Dependency: perl(DBI) for package: slony1 > --> Processing Dependency: perl-DBD-Pg for package: slony1 > --> Running transaction check > ---> Package perl-DBD-Pg.i386 0:2.11.5-1.el5.rf set to be updated > --> Processing Dependency: perl(version) for package: perl-DBD-Pg > ---> Package perl-DBI.i386 0:1.607-1.el5.rf set to be updated > --> Processing Dependency: perl(RPC::PlServer) >= 0.2001 for package: > perl-DBI > --> Processing Dependency: perl(RPC::PlClient) >= 0.2000 for package: > perl-DBI > --> Running transaction check > ---> Package perl-version.i386 0:0.74-1.el5.rf set to be updated > ---> Package perl-PlRPC.noarch 0:0.2020-1.el5.rf set to be updated > --> Processing Dependency: perl(Net::Daemon) for package: perl-PlRPC > --> Processing Dependency: perl(Net::Daemon::Log) for package: perl-PlRPC > --> Processing Dependency: perl(Net::Daemon::Test) for package: perl-PlRPC > --> Running transaction check > ---> Package perl-Net-Daemon.noarch 0:0.43-1.el5.rf set to be updated > --> Finished Dependency Resolution > > Dependencies Resolved > > ============================================================================= > Package Arch Version Repository > Size > ============================================================================= > Installing: > slony1 i386 1.2.15-3.rhel5 pgdg83 267 > k > Installing for dependencies: > perl-DBD-Pg i386 2.11.5-1.el5.rf rpmforge 301 > k > perl-DBI i386 1.607-1.el5.rf rpmforge 866 > k > perl-Net-Daemon noarch 0.43-1.el5.rf rpmforge 44 > k > perl-PlRPC noarch 0.2020-1.el5.rf rpmforge 33 > k > perl-version i386 0.74-1.el5.rf rpmforge 76 > k > > Transaction Summary > ============================================================================= > Install 6 Package(s) > Update 0 Package(s) > Remove 0 Package(s) > > Total download size: 1.6 M > Is this ok [y/N]: y > Downloading Packages: > (1/6): slony1-1.2.15-3.rh 100% |=========================| 267 kB 00:00 > (2/6): perl-PlRPC-0.2020- 100% |=========================| 33 kB 00:00 > (3/6): perl-version-0.74- 100% |=========================| 76 kB 00:00 > (4/6): perl-Net-Daemon-0. 100% |=========================| 44 kB 00:00 > (5/6): perl-DBD-Pg-2.11.5 100% |=========================| 301 kB 00:00 > (6/6): perl-DBI-1.607-1.e 100% |=========================| 866 kB 00:02 > Running rpm_check_debug > Running Transaction Test > Finished Transaction Test > Transaction Test Succeeded > Running Transaction > Installing: perl-version ######################### [1/6] > Installing: perl-Net-Daemon ######################### [2/6] > Installing: perl-PlRPC ######################### [3/6] > Installing: perl-DBI ######################### [4/6] > Installing: perl-DBD-Pg ######################### [5/6] > Installing: slony1 ######################### [6/6] > > Installed: slony1.i386 0:1.2.15-3.rhel5 > Dependency Installed: perl-DBD-Pg.i386 0:2.11.5-1.el5.rf perl-DBI.i386 > 0:1.607-1.el5.rf perl-Net-Daemon.noarch 0:0.43-1.el5.rf perl-PlRPC.noarch > 0:0.2020-1.el5.rf perl-version.i386 0:0.74-1.el5.rf > Complete! > > > > -bash-3.2# slo > slogin slonik_drop_set > slonik_subscribe_set > slon slonik_drop_table > slonik_uninstall_nodes > slon_kill slonik_execute_script > slonik_unsubscribe_set > slon_start slonik_failover > slonik_update_nodes > slon_watchdog slonik_init_cluster > slony-cluster-analysis-mass.sh > slon_watchdog2 slonik_merge_sets > slony-cluster-analysis.sh > slonik slonik_move_set > slony1_dump.sh > slonik_build_env slonik_print_preamble > slony1_extract_schema.sh > slonik_create_set slonik_restart_node > slony_logshipper > slonik_drop_node slonik_store_node > slony_show_configuration > -bash-3.2# slo > slogin slonik_drop_set > slonik_subscribe_set > slon slonik_drop_table > slonik_uninstall_nodes > slon_kill slonik_execute_script > slonik_unsubscribe_set > slon_start slonik_failover > slonik_update_nodes > slon_watchdog slonik_init_cluster > slony-cluster-analysis-mass.sh > slon_watchdog2 slonik_merge_sets > slony-cluster-analysis.sh > slonik slonik_move_set > slony1_dump.sh > slonik_build_env slonik_print_preamble > slony1_extract_schema.sh > slonik_create_set slonik_restart_node > slony_logshipper > slonik_drop_node slonik_store_node > slony_show_configuration > -bash-3.2# > > _______________________________________________ > Slony1-general mailing list > Slony1-general at lists.slony.info > http://lists.slony.info/mailman/listinfo/slony1-general > > the path for pg_config directory is same as of your postgresql data directory... like /var/lib/pgsql/data but this file is not on your system that is why slony is anable to find its path by own at the time of your instaaltion of slony you need to install postgresql-devel-8.3.5-1PGDG.rhel5.rpm and this file will be automatically generated in your data directory -- View this message in context: http://www.nabble.com/pg_config-for-slony1-install-tp21745934p22922680.html Sent from the Slony-I -- General mailing list archive at Nabble.com.
- Previous message: [Slony1-general] replication stalled.
- Next message: [Slony1-general] Slony querries.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list