pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
slony1-ctl - slony-ctl: Check return code in every script, per report by
2+ messages / 2 participants
[nested] [flat]

* slony1-ctl - slony-ctl: Check return code in every script, per report by
@ 2009-06-02 14:51  User Sas <sas@pgfoundry.org>
  0 siblings, 0 replies; 2+ messages in thread

From: sas@pgfoundry.org @ 2009-06-02 14:51 UTC (permalink / raw)
  To: pgsql-committers

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...)




^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* pgsql: docs: Consolidate into new "WAL for Extensions" chapter.
@ 2024-04-15 20:06  Robert Haas <rhaas@postgresql.org>
  0 siblings, 0 replies; 2+ messages in thread

From: Robert Haas @ 2024-04-15 20:06 UTC (permalink / raw)
  To: pgsql-committers@lists.postgresql.org

docs: Consolidate into new "WAL for Extensions" chapter.

Previously, we had consecutive, very short chapters called "Generic
WAL" and "Custom WAL Resource Managers," explaining different approaches
to the same problem. Merge them into a single chapter. Explain most
of the differences between the approaches in the chapter's
introductory text, rather than in the individual sections.

Discussion: http://postgr.es/m/46ac50c1-6b2a-404f-a683-b67af6ab56e9@eisentraut.org

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/09d9800e52822ed20d69d98aaa39d3fb10769c44

Modified Files
--------------
doc/src/sgml/custom-rmgr.sgml        | 11 ++++-------
doc/src/sgml/filelist.sgml           |  1 +
doc/src/sgml/generic-wal.sgml        | 14 +++-----------
doc/src/sgml/postgres.sgml           |  3 +--
doc/src/sgml/wal-for-extensions.sgml | 32 ++++++++++++++++++++++++++++++++
5 files changed, 41 insertions(+), 20 deletions(-)



^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2024-04-15 20:06 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2009-06-02 14:51 slony1-ctl - slony-ctl: Check return code in every script, per report by User Sas <sas@pgfoundry.org>
2024-04-15 20:06 pgsql: docs: Consolidate into new "WAL for Extensions" chapter. Robert Haas <rhaas@postgresql.org>

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