Re: Changing postgresql.conf values without restarting the postmaster?

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Vitaly Belman" <vitalybe(at)yahoo(dot)com>, "PgSql-Win32" <pgsql-hackers-win32(at)postgresql(dot)org>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Subject: Re: Changing postgresql.conf values without restarting the postmaster?
Date: 2004-05-19 15:15:27
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCE34BA62@algol.sollentuna.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers-win32

> > 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

Browse pgsql-hackers-win32 by date

  From Date Subject
Next Message Jason Priebe 2004-05-20 17:08:08 large objects issue
Previous Message Tom Lane 2004-05-19 15:12:53 Re: Changing postgresql.conf values without restarting the postmaster?