From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Zdenek Kotala <zdenek(dot)kotala(at)sun(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: What default is - SET behavior |
Date: | 2006-05-17 13:49:19 |
Message-ID: | 200605171349.k4HDnJJ15868@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Zdenek Kotala wrote:
> I'm interesting in problem "Allow commenting of variables in
> postgresql.conf to restore them to defaults". And I need some clarify
> of SET command behavior.
>
> Res_value is defined in the source code as highest overriding setting
> during startup (or reconfiguration) and it is used for store "default"
> value. Hovewer documentation of SET command
> (http://www.postgresql.org/docs/8.1/interactive/sql-set.html) talk about
> "DEFAULT can be used to specify resetting the parameter to its default
> value." And there is question what is the meaning of "default value".
> Because I understood "default" like value coded in source code -
> mentioned in the postgresql.conf.
DEFAULT in this case is session default, which might be the compiled in
default, which can be over-ridden by postgresql.conf, or by a user user
SET command on session start (ALTER USER SET).
--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-05-17 14:01:18 | Re: does wal archiving block the current client connection? |
Previous Message | Zdenek Kotala | 2006-05-17 13:44:22 | What default is - SET behavior |