Re: Improving postgresql.conf
| От | Christopher Kings-Lynne |
|---|---|
| Тема | Re: Improving postgresql.conf |
| Дата | |
| Msg-id | 40CFC703.5010603@familyhealth.com.au обсуждение исходный текст |
| Ответ на | Re: Improving postgresql.conf (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Improving postgresql.conf
Re: Improving postgresql.conf |
| Список | pgsql-hackers |
>>The proposal is to remove the comments from postgresql.conf (like >>Apache) so all entries will be active. The downside is that it will not >>be possible to determine which values were modified from their defaults. One thing that truly annoys me about postgresql.conf is say I unhash an option and set it to something. Then I reload. Then I edit the conf and hash it out again, then I reload. Of course, the option still has my old value. This is really annoying and I've wasted lots of time trying to figure out what's going on. Chris
В списке pgsql-hackers по дате отправления: