Re: GUC and postgresql.conf docs
От | Josh Berkus |
---|---|
Тема | Re: GUC and postgresql.conf docs |
Дата | |
Msg-id | 200305121040.06064.josh@agliodbs.com обсуждение исходный текст |
Ответ на | Re: GUC and postgresql.conf docs (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: GUC and postgresql.conf docs
|
Список | pgsql-hackers |
Tom, > The tables in src/backend/utils/misc/guc.c are the authoritative reference. > Read the comments in src/include/utils/guc.h first. Thanks. Would never have found it on my own ... > Yes, everything in postgresql.conf is a GUC variable; but I think there > may be some GUC variables that were omitted from postgresql.conf. > Hopefully intentionally, not by oversight ... Mmm? I think I have some terminology confusion somewhere. I thought that a GUC variable meant that it could be changed through a SET statement. But some settings, like TCP/IP socket, cannot be SET. What distinguises settings that can be SET from GUC variables that are restart-only? I sense more posts to the list in the offing. -- Josh Berkus Aglio Database Solutions San Francisco
В списке pgsql-hackers по дате отправления: