| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
Because we rely on parsing of `systemctl show -p` outuput heavily,
we need to detect whether the service file or some dropin did not
change (or was not added). So from now we rather instruct admin
to do daemon-reload when something changed..
* postgresql-setup.in: Detect the NeedDaemonReload and warn if
yes.
* NEWS: Document.
|
| |
|
|
|
|
|
|
| |
* postgresql-setup.in (USAGE_STRING): Mention --port option.
(initdb): Mention in info output the non-standard port, when used.
* postgresql-setup.in: Do not throw the default-port message
always, remved remaining sysconfig leftover.
* NEWS: Mention that env files are now supported.
|
| |
|
|
| |
(and bump version to 0.9.2~beta)
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If user removes currently provided /etc/postgresql/postgresql
configuration file, PGDATA env variable is not set. The
`systemctl start postgresql` would fail similarly to
`systemctl start postgresql@NOTCONFIGURED` when the configuration
file was not created yet with cryptic message
"Usage: ... "
Stop this behavior rather explicitly with proper error in
check-db-dir script.
Warn also user in similar fashion that the configuration should be
adjusted in case the PGDATA was set directly in service file.
|
| |
|
|
|
|
| |
Follow the new processes - different options of postgresql-setup,
instantiable unit files. Simplify the documentation thanks to
the template.
|
| |
|
|
| |
Merge changes with ChangeLog & NEWS files. Bump version.
|
|
|
This makes us to do some additional documentation, but it should
not be so hard.
|
