On Jan 19, 2010, at 2:57 PM, Tom Lane wrote:
> Ben Chobot writes:
>> Shouldn't the source change to "config file" after the reset?
>
> Not within the same session. ALTER DATABASE and ALTER USER settings
> are only examined at session startup.
OK, things are working as expected now. Thanks!
-
Ben Chobot writes:
> Shouldn't the source change to "config file" after the reset?
Not within the same session. ALTER DATABASE and ALTER USER settings
are only examined at session startup.
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgres
On Jan 19, 2010, at 2:32 PM, Tom Lane wrote:
> You might try looking at the pg_settings row for the variable to see
> what it says the source is.
That's interesting:
foo# select source from pg_settings where name='log_min_duration_statement';
source
--
database
foo# alter database
Ben Chobot writes:
> On Jan 19, 2010, at 1:44 PM, Devrim GÜNDÜZ wrote:
>> Also, a distro (Gentoo) has 2 conf files which overrides some settings
>> in postgresql.conf -- you may suffer from something similar.
> Not to my knowledge. I'm on debian, and I'm editing the file listed in
> config_file.
On Jan 19, 2010, at 1:44 PM, Devrim GÜNDÜZ wrote:
> What do you get after reloading server and running
>
> psql -c "SHOW log_min_duration_statement"
The same value that was there before the reload.
> Maybe there are more than one log_min_duration_statement in
> postgresql.conf?
Nope. (Or, mor
On Tue, 2010-01-19 at 13:27 -0800, Ben Chobot wrote:
>
> I'm having difficulties with one of my 8.1.19 installs.
> log_min_duration_statement is currently set to 500. I would like to
> change it to 0. Changing it in the config file and sending a HUP to
> the postmaster has no effect.
What do you
