Thank you for the report, also in bug 26241.
This is already fixed in Cauldron for postgresql11, thanks David G:
 Sun Feb 23 05:07:27 2020 UTC (mga#26240)
- switch tmpfiles dir from /var/run to /run/postgresql
But I cannot find the equivalent for 9.6 or 10.
Assigning globally for 9.6, CC MarcK for 11; DavidG for the 11 fix.

Assignee: bugsquad => pkg-bugs
CC: (none) => geiger.david68210, mageia
Source RPM: postgresql9.6-9.6.17-1.mga7.src.rpm => postgresql9.6-9.6.17-1.mga7.src.rpm, postgresql11-11.7-1.mga7.src.rpm

*** Bug 26241 has been marked as a duplicate of this bug. ***

Updated postgresql packages 9.6 and 11:
shipped packages still used legacy directory /var/run instead of /run

Updated packages in core/updates_testing:
========================
9.6:
postgresql9.6-9.6.17-2.mga7
lib64pq5.9-9.6.17-2.mga7
lib64ecpg9.6_6-9.6.17-2.mga7
postgresql9.6-server-9.6.17-2.mga7
postgresql9.6-docs-9.6.17-2.mga7
postgresql9.6-contrib-9.6.17-2.mga7
postgresql9.6-devel-9.6.17-2.mga7
postgresql9.6-pl-9.6.17-2.mga7
postgresql9.6-plpython-9.6.17-2.mga7
postgresql9.6-plperl-9.6.17-2.mga7
postgresql9.6-pltcl-9.6.17-2.mga7
postgresql9.6-plpgsql-9.6.17-2.mga7
postgresql9.6-debugsource-9.6.17-2.mga7
postgresql9.6-debuginfo-9.6.17-2.mga7
lib64pq5.9-debuginfo-9.6.17-2.mga7
lib64ecpg9.6_6-debuginfo-9.6.17-2.mga7
postgresql9.6-server-debuginfo-9.6.17-2.mga7
postgresql9.6-contrib-debuginfo-9.6.17-2.mga7
postgresql9.6-devel-debuginfo-9.6.17-2.mga7
postgresql9.6-plpython-debuginfo-9.6.17-2.mga7
postgresql9.6-plperl-debuginfo-9.6.17-2.mga7
postgresql9.6-pltcl-debuginfo-9.6.17-2.mga7
postgresql9.6-plpgsql-debuginfo-9.6.17-2.mga7


11:
postgresql11-11.7-2.mga7
libpq5-11.7-2.mga7
libecpg11_6-11.7-2.mga7
postgresql11-server-11.7-2.mga7
postgresql11-docs-11.7-2.mga7
postgresql11-contrib-11.7-2.mga7
postgresql11-devel-11.7-2.mga7
postgresql11-pl-11.7-2.mga7
postgresql11-plpython-11.7-2.mga7
postgresql11-plpython3-11.7-2.mga7
postgresql11-plperl-11.7-2.mga7
postgresql11-pltcl-11.7-2.mga7
postgresql11-plpgsql-11.7-2.mga7
postgresql11-debugsource-11.7-2.mga7
postgresql11-debuginfo-11.7-2.mga7
libpq5-debuginfo-11.7-2.mga7
libecpg11_6-debuginfo-11.7-2.mga7
postgresql11-server-debuginfo-11.7-2.mga7
postgresql11-contrib-debuginfo-11.7-2.mga7
postgresql11-devel-debuginfo-11.7-2.mga7
postgresql11-plpython-debuginfo-11.7-2.mga7
postgresql11-plpython3-debuginfo-11.7-2.mga7
postgresql11-plperl-debuginfo-11.7-2.mga7
postgresql11-pltcl-debuginfo-11.7-2.mga7
postgresql11-plpgsql-debuginfo-11.7-2.mga7

SRPM:
postgresql9.6-9.6.17-2.mga7.src.rpm
postgresql11-11.7-2.mga7.src.rpm

Assignee: mageia => qa-bugs

MGA7-64 Plasma on Lenovo B50
Intalled 9.6
Using pgadminIII, deleted table from previous test, and created a new one, works OK.
Checked change in /usr/lib/tmpfiles.d/postgresql.conf, is OK.
Continuing by removing 9.6 and nstalling 11.

CC: (none) => herman.viaene

Deleted 9.6 and its data (necessary since this version would not install with a 9.6 database present)
Installed without further issues.
Could not connect with pgadminIII , warning was given that this only works up to 9.6
first at CLI:
su -l postgres (after unlocking)
createdb test1172
create role tester11 login password '<xxxx>'
used the user to login in phpPgAdmin and create a table with a PK and a unique key
Checked change in /usr/lib/tmpfiles.d/postgresql.conf, is OK.
Good enough for me.

Whiteboard: (none) => MGA7-64-OK

Validating. Advisory in Comment 3.

Keywords: (none) => validated_update
CC: (none) => andrewsfarm, sysadmin-bugs

So why was this not caught and fixed in bug 26196 that we pushed one week ago ?

And if it was not important enough to fix then, why is it now ?

Could it not have been fixed in svn and just waiting for the next update...

Oh well...

CC: (none) => tmb
Keywords: (none) => advisory

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2020-0067.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED