Hi Marco,
Just FYI there appears to be a bug in the package's scripts as per
the below output. If I manually delete the dead symlink at
'/etc/rc2.d/S20repmgrd' then it upgrades from 4.0.0 to 4.0.1 without any
errors.
Thanks
Jonathan
# apt-get install postgresql-9.5-repmgr
Reading package lists... Done
Building dependency tree
Reading state information... Done
postgresql-9.5-repmgr is already the newest version.
The following packages will be upgraded:
repmgr-common
1 upgraded, 0 newly installed, 0 to remove and 69 not upgraded.
2 not fully installed or removed.
Need to get 0 B/87.1 kB of archives.
After this operation, 4,096 B of additional disk space will be used.
(Reading database ... 40843 files and directories currently installed.)
Preparing to unpack .../repmgr-common_4.0.1-1.pgdg14.04+1_all.deb ...
invoke-rc.d: dangling symlink: /etc/rc2.d/S20repmgrd
dpkg: warning: subprocess old pre-removal script returned error exit
status 102
dpkg: trying script from the new package instead ...
invoke-rc.d: dangling symlink: /etc/rc2.d/S20repmgrd
dpkg: error processing archive
/var/cache/apt/archives/repmgr-common_4.0.1-1.pgdg14.04+1_all.deb
(--unpack):
subprocess new pre-removal script returned error exit status 102
invoke-rc.d: dangling symlink: /etc/rc2.d/S20repmgrd
dpkg: error while cleaning up:
subprocess installed post-installation script returned error exit
status 102
Errors were encountered while processing:
/var/cache/apt/archives/repmgr-common_4.0.1-1.pgdg14.04+1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
On 05/12/17 15:46, Marco Nenciarini wrote:
> Il 05/12/17 16:30, Jonathan Heard ha scritto:
>> Hi Marco,
>>
>> We've taken the decision to upgrade to repmgr 4.x because sticking
>> with the old version is complex and leaves us 'frozen in time' without
>> any updates etc..
>>
>> Unfortunately, I've hit a show-stopped bug in version 4 :-( The repo
>> gives us 4.0.0-2.pgdg14.04+2 but the SQL query for 'repmgr cluster show'
>> is broken. We don't use the 'repmgr' user and have fallen foul of the
>> oversight which is fixed the following commit:
>>
>> | * commit 3e4a5e6ff5f386391c06aa639fbd8ff6299e1db6
>> | | Author: Martín Marqués <martin.marques@2ndquadrant.com>
>> | | Date: Wed Nov 22 17:13:58 2017 -0300
>> | |
>> | | Fix missing FQN for the nodes table.
>> | |
>> | | This bug was not detected before because most users work with
>> the repmgr
>> | | user. For that reason, the repmgr schema is already in the
>> search_path
>> | | by default.
>> | |
>> | | Add the repmgr schema to the nodes table in the LEFT JOIN used for
>> | | cluster show (and in other places)
>>
>> The above commit is is rolled up into v4.0.1 so do you know when this
>> will be released to the PPA please?
>>
> AFAIK the 4.0.1 release is scheduled for the next week.
>
> Regards,
> Marco
>