--- Begin Message ---
Subject: |
postgresql-service error checking wtf |
Date: |
Wed, 10 Feb 2016 20:01:43 +0100 |
Package: postgresql
When I first configure operating-system with postgresql-service with default
config file, then run
guix system reconfigure config.scm,
then configure operating-system with postgresql-service with custom config
file, then run
guix system reconfigure config.scm,
I get:
---
initdb: directory "/var/lib/postgresql/data" exists but is not empty
If you want to create a new database system, either remove or empty
the directory "/var/lib/postgresql/data" or run initdb
with an argument other than "/var/lib/postgresql/data".
making '/gnu/store/byn534fg4agm0vv9szl5kkfl19n080b2-system' the current
system...
Installation finished. No error reported.
----
Postgresql doesn't run and the error message still references the default
config file.
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#22619: postgresql-service error checking wtf |
Date: |
Sun, 21 Feb 2016 12:38:03 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Danny Milosavljevic <address@hidden> skribis:
> The actual problem only arises because guix reconfigure doesn't deem a change
> in service arguments as reason to restart (or reconfigure) a service.
>
> I.e. before, my config was:
>
> (postgresql-service )
>
> Then I did guix reconfigure ...
>
> Afterwards, I changed the config to:
>
> (postgresql-service #:config-file ...)
>
> Then I did giux reconfigure # this erroneously doesn't reload the postgres
> service!!
Yes, this is a known limitation: <http://bugs.gnu.org/22039>.
Currently, for services that are safe to be restarted, the solution is
to explicitly stop them beforehand, in which case the new service gets
started by ‘guix system reconfigure’:
# herd stop postgresql
# guix system reconfigure new-config.scm
I’m closing this bug. Let me know if anything else is amiss.
Thanks,
Ludo’.
--- End Message ---