Bug 99815 – Sensible default setting for PostgreSQL missing

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Ole Tange 2005-07-21 10:18:05 UTC]

On a clean system I emerged Postgresql. I would expect that running 
 
  /etc/init.d/postgresql start 
 
would start the database with sensible default values. 
 
 

Reproducible: Always
Steps to Reproduce:
1. New system 
2. emerge postgresql 
3. /etc/init.d/postgresql start 
 
 
 
Actual Results:  
/etc/init.d/postgresql start 
 * Caching service dependencies ...                                                                                   
[ ok ] 
 * directory not found: /var/lib/postgresql/data 
 * You should create PGDATA directory first. 
 
After creating PGDATA: 
 
/etc/init.d/postgresql start 
 * Starting PostgreSQL ... 
sh: /var/lib/postgresql/data/postgresql.log: Permission denied 
 * Please see log file: /var/lib/postgresql/data/postgresql.log                   
 
After setting the correct permission on PGDATA: 
 
/etc/init.d/postgresql start 
 * Starting PostgreSQL ... 
 * Please see log file: /var/lib/postgresql/data/postgresql.log 
 
Looking at: /var/lib/postgresql/data/postgresql.log 
postmaster cannot access the server configuration file 
"/var/lib/postgresql/data/postgresql.conf": No such file or directory 
 

Expected Results:  
Postgresql should have started. To any configuration question assume that the 
user will answer "I do not care. Give me a sensible default". 
 
The users who cannot live with sensible default will tweak the system anyway, 
so it will not be more trouble for them.

[Comment 1 Ole Tange 2005-07-21 10:24:28 UTC]

It seems I have to run: 
 
  ebuild /var/db/pkg/dev-db/postgresql-8.0.1-r4/postgresql-8.0.1-r4.ebuild 
config 
 
Why is this not done automatically? 
 
 

[Comment 2 Jakub Moc (RETIRED) 2005-07-21 10:29:58 UTC]

Closing as invalid, failure to follow the instructions is not a bug.

[Comment 3 Ole Tange 2005-07-21 10:56:48 UTC]

When installing a package that depends on a package that depends on PostgreSql 
it is impossible to see the instructions. 
 
And since PostgreSQL is unsuable before executing the command, why not make it 
the default to execute the command automatically? 
 

[Comment 4 Jakub Moc (RETIRED) 2005-07-21 11:06:33 UTC]

(In reply to comment #3)
> When installing a package that depends on a package that depends on PostgreSql 
> it is impossible to see the instructions. 

See Bug 11359. 

> And since PostgreSQL is unsuable before executing the command, why not make it 
> the default to execute the command automatically? 

Because the ebuild config stuff is only usefull when installing, not when
upgrading.