pg.ddx.io pgsql-committers@postgresql.org mailing list archive help / color / mirror / Atom feed From: sas@pgfoundry.org
To: pgsql-committers@postgresql.org
Subject: slony1-ctl - slony-ctl: Check return code in every script, per report by
Date: Tue, 2 Jun 2009 14:51:36 +0000 (UTC)
Message-ID: <20090602145136.C001C17ADF5D@pgfoundry.org> (raw )
Log Message:
-----------
Check return code in every script, per report by Bastian Voigt
Modified Files:
--------------
slony-ctl/outils:
02_exec_init.sh (r1.7 -> r1.8)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/02_exec_init.sh?r1=1.7&r... )
21_create_addnode.sh (r1.3 -> r1.4)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/21_create_addnode.sh?r1=1.3&... )
51_create_upgrade.sh (r1.3 -> r1.4)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/51_create_upgrade.sh?r1=1.3&... )
52_exec_upgrade.sh (r1.3 -> r1.4)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/52_exec_upgrade.sh?r1=1.3&am... )
62_exec_subscribe.sh (r1.3 -> r1.4)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/62_exec_subscribe.sh?r1=1.3&... )
71_create_path.sh (r1.3 -> r1.4)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/71_create_path.sh?r1=1.3&... )
72_exec_path.sh (r1.3 -> r1.4)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/72_exec_path.sh?r1=1.3&r... )
82_exec_switch.sh (r1.3 -> r1.4)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/82_exec_switch.sh?r1=1.3&... )
92_exec_fail.sh (r1.4 -> r1.5)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/92_exec_fail.sh?r1=1.4&r... )
aff_tree.sh (r1.3 -> r1.4)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/aff_tree.sh?r1=1.3&r2=1.... )
create_preamble.sh (r1.2 -> r1.3)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/create_preamble.sh?r1=1.2&am... )
create_slon.sh (r1.2 -> r1.3)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/create_slon.sh?r1=1.2&r2... )
create_struct.sh (r1.2 -> r1.3)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/create_struct.sh?r1=1.2&... )
slony_addnode.sh (r1.3 -> r1.4)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/slony_addnode.sh?r1=1.3&... )
slony_addobj.sh (r1.2 -> r1.3)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/slony_addobj.sh?r1=1.2&r... )
slony_ctl.sh (r1.2 -> r1.3)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/slony_ctl.sh?r1=1.2&r2=1... )
slony_dropobj.sh (r1.1 -> r1.2)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/slony_dropobj.sh?r1=1.1&... )
slony_execute.sh (r1.3 -> r1.4)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/slony_execute.sh?r1=1.3&... )
slony_fail.sh (r1.4 -> r1.5)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/slony_fail.sh?r1=1.4&r2=... )
slony_merge.sh (r1.2 -> r1.3)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/slony_merge.sh?r1=1.2&r2... )
slony_path.sh (r1.3 -> r1.4)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/slony_path.sh?r1=1.3&r2=... )
slony_repstat.sh (r1.2 -> r1.3)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/slony_repstat.sh?r1=1.2&... )
slony_switch.sh (r1.3 -> r1.4)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/slony_switch.sh?r1=1.3&r... )
tree.sh (r1.3 -> r1.4)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/tree.sh?r1=1.3&r2=1.4 )
upgrade_slon.sh (r1.2 -> r1.3)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/upgrade_slon.sh?r1=1.2&r... )
view thread (2+ messages) latest in thread
Message-ID: <20090602145136.C001C17ADF5D@pgfoundry.org>
Permalink: ../20090602145136.C001C17ADF5D@pgfoundry.org/
Also on: postgresql.org/message-id/20090602145136.C001C17ADF5D@pgfoundry.org
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: sas@pgfoundry.org
Subject: Re: slony1-ctl - slony-ctl: Check return code in every script, per report by
In-Reply-To: <20090602145136.C001C17ADF5D@pgfoundry.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox