Re: .conf File Organization
От | Josh Berkus |
---|---|
Тема | Re: .conf File Organization |
Дата | |
Msg-id | 200706121249.06313.josh@agliodbs.com обсуждение исходный текст |
Ответ на | Re: .conf File Organization WAS: Controlling Load Distributed Checkpoints (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: .conf File Organization
|
Список | pgsql-hackers |
Tom, > Do you have a better organizing principle than what's there now? It's mostly detail stuff: putting VACUUM and Autovac together, breaking up some subsections that now have too many options in them into grouped. Client Connection Defaults has somehow become a catchall secton for *any* USERSET variable, regardless of purpose. I'd like to trim it back down and assign some of those variables to appropriate sections. On the more hypothetical basis I was thinking of adding a section at the top with the 7-9 most common options that people *need* to set; this would make PostgreSQL.conf much more accessable but would result in duplicate options which might cause some issues. -- Josh Berkus PostgreSQL @ Sun San Francisco
В списке pgsql-hackers по дате отправления: