Обсуждение: Changing postgresql.conf values without restarting the postmaster?

It says:

# This file is read on postmaster startup and when the
postmaster
# receives a SIGHUP.

How do I send a SIGHUP to the postmaster in Win32? Or
is there another way?




__________________________________
Do you Yahoo!?
SBC Yahoo! - Internet access at a great low price.
http://promo.yahoo.com/sbc/

> # This file is read on postmaster startup and when the
> postmaster # receives a SIGHUP.
>
> How do I send a SIGHUP to the postmaster in Win32? Or is
> there another way?


Use the "pgkill" utility available on
http://momjian.postgresql.org/main/writings/pgsql/win32.html


//Magnus

Thanks but it didn't seem to work too well... I
compiled and sent the SIGHUP, postmaster said:

> LOG:  received SIGHUP, reloading configuration files

Which is great but then it started an infinite loop
of:

> FATAL:  parameter "lc_collate" cannot be changed

Anyone know what's it?

--- Magnus Hagander <mha@sollentuna.net> wrote:
> > # This file is read on postmaster startup and when
> the
> > postmaster # receives a SIGHUP.
> >
> > How do I send a SIGHUP to the postmaster in Win32?
> Or is
> > there another way?
>
>
> Use the "pgkill" utility available on
>
http://momjian.postgresql.org/main/writings/pgsql/win32.html
>
>
> //Magnus
>





__________________________________
Do you Yahoo!?
SBC Yahoo! - Internet access at a great low price.
http://promo.yahoo.com/sbc/

Ok. I see the problem whit this. I'm not 100% sure on the fix, though.

The problem is that write_nondefault_variables() writes out variables of
type PGC_INTERNAL. I've attached a patch that simply prevents it from
doing this. It does make the problem go away, and I *think* it should be
safe, but I'm not totally sure...

//Magnus


>-----Original Message-----
>From: Vitaly Belman [mailto:vitalybe@yahoo.com]
>Sent: den 14 maj 2004 19:34
>To: Magnus Hagander; PgSql-Win32
>Subject: RE: [pgsql-hackers-win32] Changing postgresql.conf
>values without restarting the postmaster?
>
>
>Thanks but it didn't seem to work too well... I
>compiled and sent the SIGHUP, postmaster said:
>
>> LOG:  received SIGHUP, reloading configuration files
>
>Which is great but then it started an infinite loop
>of:
>
>> FATAL:  parameter "lc_collate" cannot be changed
>
>Anyone know what's it?
>
>--- Magnus Hagander <mha@sollentuna.net> wrote:
>> > # This file is read on postmaster startup and when
>> the
>> > postmaster # receives a SIGHUP.
>> >
>> > How do I send a SIGHUP to the postmaster in Win32?
>> Or is
>> > there another way?
>>
>>
>> Use the "pgkill" utility available on
>>
>http://momjian.postgresql.org/main/writings/pgsql/win32.html
>>
>>
>> //Magnus
>>
>
>
>
>
>
>__________________________________
>Do you Yahoo!?
>SBC Yahoo! - Internet access at a great low price.
>http://promo.yahoo.com/sbc/
>

"Magnus Hagander" <mha@sollentuna.net> writes:
> The problem is that write_nondefault_variables() writes out variables of
> type PGC_INTERNAL. I've attached a patch that simply prevents it from
> doing this. It does make the problem go away, and I *think* it should be
> safe, but I'm not totally sure...

The issue then is whether there are other mechanisms in place to ensure
that backends correctly inherit the values associated with these
variables...

            regards, tom lane

> > The problem is that write_nondefault_variables() writes out
> variables
> > of type PGC_INTERNAL. I've attached a patch that simply prevents it
> > from doing this. It does make the problem go away, and I *think* it
> > should be safe, but I'm not totally sure...
>
> The issue then is whether there are other mechanisms in place
> to ensure that backends correctly inherit the values
> associated with these variables...

Yup. In this case, it's the locale stuff. I'm on that one. While I do
that one, I'll see if I can look over the rest of the PGC_INTERNALs.

//Magnus