[Pkg-postgresql-public] Bug#838641: pg_renamecluster doesn't rollback on failure

Petr Cech cech at flora.cechovi.org
Fri Sep 23 08:35:30 UTC 2016

Package: postgresql-common
Version: 175
Severity: normal

I was renaming cluster maincrc to main, but forgot to move old data directory. The script has detected, that an old dir is there, but the config directory in /etc was already renamed.

I think, that upon failure the renaming of the config directory should be rolled back.

On a side note, the script should also rename the new 9.6 setting `cluster_name'.


-- System Information:
Debian Release: stretch/sid
  APT prefers proposed-updates
  APT policy: (550, 'proposed-updates'), (550, 'stable'), (500, 'stable-updates'), (500, 'testing'), (99, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages postgresql-common depends on:
ii  adduser                   3.115
ii  debconf [debconf-2.0]     1.5.59
ii  init-system-helpers       1.45
ii  lsb-base                  9.20160629
ii  postgresql-client-common  175
ii  procps                    2:3.3.12-2
ii  ssl-cert                  1.0.38
ii  ucf                       3.0036

Versions of packages postgresql-common recommends:
ii  logrotate  3.9.1-1~exp1

postgresql-common suggests no packages.

-- Configuration Files:
/etc/postgresql-common/createcluster.conf changed [not included]

-- debconf information excluded

More information about the Pkg-postgresql-public mailing list