Your message dated Thu, 8 Aug 2019 16:49:26 +0200
with message-id <[email protected]>
and subject line Re: Bug#932675: postgres: Changing of data_directory does not
work
has caused the Debian Bug report #932675,
regarding postgres: Changing of data_directory does not work
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
932675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932675
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: postgresql-11
Version: 11.4-1
Severity: important
File: postgres
Dear Maintainer,
I upgraded my system to buster. Than I upgraded my pg-cluster from 9.6
to 11. After this I wanted to change the data_directory to an other
mount point. Before the update the old cluster was there, too.
I did these steps:
1. stop the service: service postgresql stop
2. change the config file: vim /etc/postgresql/11/main/postgresql.conf
- data_directory = '/var/lib/postgresql/11/main'
+ data_directory = '/media/postgresql/data/11/main'
3. I moved the data from the default path to the new one
4. start the service: service postgresql start
I got these logs:
Jul 21 21:30:33 zotac systemd[1]: Stopping PostgreSQL RDBMS...
Jul 21 21:30:33 zotac systemd[1]: Starting PostgreSQL Cluster 11-main...
Jul 21 21:30:33 zotac postgresql@11-main[22961]: Error:
/var/lib/postgresql/11/main is not accessible or does not exist
Jul 21 21:30:33 zotac systemd[1]: [email protected]: Can't open PID
file /run/postgresql/11-main.pid (yet?) after start: No such file or directory
Jul 21 21:30:33 zotac systemd[1]: [email protected]: Failed with
result 'protocol'.
Jul 21 21:30:33 zotac systemd[1]: Failed to start PostgreSQL Cluster 11-main.
Jul 21 21:30:33 zotac systemd[1]: Starting PostgreSQL RDBMS...
Jul 21 21:30:33 zotac systemd[1]: Started PostgreSQL RDBMS.
There you can see, that my changed path was not reconised.
-- System Information:
Debian Release: 10.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages postgresql-11 depends on:
ii debconf [debconf-2.0] 1.5.71
ii libc6 2.28-10
ii libgcc1 1:8.3.0-6
ii libgssapi-krb5-2 1.17-3
ii libicu63 63.1-6
ii libldap-2.4-2 2.4.47+dfsg-3
ii libllvm7 1:7.0.1-8
ii libpam0g 1.3.1-5
ii libpq5 11.4-1
ii libselinux1 2.8-1+b1
ii libssl1.1 1.1.1c-1
ii libstdc++6 8.3.0-6
ii libsystemd0 241-5
ii libuuid1 2.33.1-0.1
ii libxml2 2.9.4+dfsg1-7+b3
ii libxslt1.1 1.1.32-2
ii locales 2.28-10
ii postgresql-client-11 11.4-1
ii postgresql-common 200+deb10u1
ii ssl-cert 1.0.39
ii tzdata 2019a-1
ii zlib1g 1:1.2.11.dfsg-1
Versions of packages postgresql-11 recommends:
ii sysstat 12.0.3-2
postgresql-11 suggests no packages.
-- debconf information excluded
--- End Message ---
--- Begin Message ---
Re: To Georg Limbach 2019-07-22 <[email protected]>
> that's a side-effect of bug #931635. After pg_upgrading the cluster,
> the postgresql.auto.conf file will have a data_directory setting as
> well.
>
> To fix, edit /media/postgresql/data/11/main/postgresql.auto.conf and
> remove the data_directory line.
>
> I'll prepare a fix for #931635 over the next days and will also see if
> we can fix this one as well.
Hi,
I decided not to separately fix this. #931635 has been scheduled to be
fixed in buster, so this problem will not happen again.
Christoph
--- End Message ---