| 2006-04-01 21:17:36 |
Murray Cumming |
bug |
|
|
added bug |
| 2006-04-03 17:07:49 |
Martin Pitt |
postgresql-8.1: status |
Unconfirmed |
Needs Info |
|
| 2006-04-03 17:07:49 |
Martin Pitt |
postgresql-8.1: statusexplanation |
|
Did you modify pg_hba.conf? I strongly assume that the password prompt is from psql, not from su. The postgres user must be able to access the cluster without a database, see the default pg_hba.conf:
# DO NOT DISABLE!
# If you change this first entry you will need to make sure that the
# database
# super user can access the database using some other method.
# Noninteractive
# access to all databases is required during automatic maintenance
# (autovacuum, daily cronjob, replication, and similar tasks).
#
# Database administrative login by UNIX sockets
local all postgres ident sameuser
|
|
| 2006-04-04 11:12:20 |
Martin Pitt |
postgresql-common: status |
Needs Info |
Confirmed |
|
| 2006-04-04 11:12:20 |
Martin Pitt |
postgresql-common: assignee |
|
pitti |
|
| 2006-04-04 11:12:20 |
Martin Pitt |
postgresql-common: statusexplanation |
Did you modify pg_hba.conf? I strongly assume that the password prompt is from psql, not from su. The postgres user must be able to access the cluster without a database, see the default pg_hba.conf:
# DO NOT DISABLE!
# If you change this first entry you will need to make sure that the
# database
# super user can access the database using some other method.
# Noninteractive
# access to all databases is required during automatic maintenance
# (autovacuum, daily cronjob, replication, and similar tasks).
#
# Database administrative login by UNIX sockets
local all postgres ident sameuser
|
If you merely remove (not purge) a package, all the clusters and their configuration will remain in place.
I see that the handling of this could be improved. The start scripts should check whether this line is still in place and complain loudly if not. In that case the checks for successful startup can just be inhibited, to avoid this password prompt, and instead there should be a meaningful error message. |
|
| 2006-04-04 11:12:44 |
Martin Pitt |
title |
post-install asks for password |
avoid password prompt if cluster owner can't connect without password |
|
| 2006-05-01 12:13:01 |
Martin Pitt |
postgresql-common: status |
Confirmed |
Fix Committed |
|
| 2006-05-01 12:13:01 |
Martin Pitt |
postgresql-common: statusexplanation |
If you merely remove (not purge) a package, all the clusters and their configuration will remain in place.
I see that the handling of this could be improved. The start scripts should check whether this line is still in place and complain loudly if not. In that case the checks for successful startup can just be inhibited, to avoid this password prompt, and instead there should be a meaningful error message. |
Fixed in my development version. Will upload in the near future. |
|
| 2006-05-11 08:10:24 |
Martin Pitt |
postgresql-common: statusexplanation |
Fixed in my development version. Will upload in the near future. |
|
|
| 2006-05-11 10:15:21 |
Martin Pitt |
postgresql-common: status |
Fix Committed |
Fix Released |
|
| 2006-05-11 10:15:21 |
Martin Pitt |
postgresql-common: statusexplanation |
|
postgresql-common (51ubuntu1) dapper; urgency=low
.
* Synchronize to Debian. Closes: LP#37640
.
postgresql-common (51) unstable; urgency=low
.
* PgCommon.pm: Add function read_pg_hba() to parse pg_hba.conf.
* Add t/005_PgCommon.t: Designated for testing PgCommon.pm library
functions; test read_pg_hba() for now.
* pg_ctlcluster: Check pg_hba.conf if the database superuser can connect
locally without a password. If not, disable startup checks to avoid asking
for the superuser password. (https://launchpad.net/bugs/37640)
* t/030_errors.t: Test above pg_ctlcluster checks.
|
|
