| Summary: | dev-db/postgresql default conf.d should not override max_connections and shared_buffers | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Marti Raudsepp <marti> |
| Component: | New packages | Assignee: | PgSQL Bugs <pgsql-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | jakub |
| Priority: | High | ||
| Version: | 2007.0 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Patch to dev-db/postgresql/files/postgresql.conf-8.2 | ||
|
Description
Marti Raudsepp
2008-01-21 00:29:02 UTC
Changing this will breaks *BSD, see Bug 189141. (In reply to comment #1) > Changing this will breaks *BSD, see Bug 189141. As far as I can tell, bug 189141 was actually *caused* because Gentoo overrides the values set in the postgresql.conf file. If the conf.d script hadn't explicitly set the -N value, PostgreSQL would have used the one determined by initdb for that particular system. The documentation states: "The default is typically 100 connections, but may be less if your kernel settings will not support it (as determined during initdb)." http://www.postgresql.org/docs/8.2/interactive/runtime-config-connection.html#GUC-MAX-CONNECTIONS Created attachment 141423 [details, diff]
Patch to dev-db/postgresql/files/postgresql.conf-8.2
Maybe I wasn't being clear enough; What I meant was, I would like to see PGOPTS value unset by default altogether.
We don't do that again in dev-db/postgresql-server |