Re: [GENERAL] wishlist: dynamic log volume control
On Thu, 19 Feb 2004, Ed L. wrote: > On Thursday February 19 2004 9:13, Bruce Momjian wrote: > > > > > > The 7.3.4 doc (doc/html/runtime-config.html) does say the > > > log_connections option can only be set at server start or in the > > > postgresql.conf configuration file. That seems a little ambiguous on > > > the SIGHUP'ability of that option. My 7.3.4 install here shows all the > > > log_* options are dynamically reloadable. > > > > The issue is that you can't set log_connections from psql. Should we > > improve the doc wording? > > Ah, I had no idea that was the issue. Maybe a quick reference > table in the docs would be helpful: > > Option SET option Reloads on SIGHUP > = > shared_buffers no no > log_connectionsno yes > log_statement yesyes > ... > > Maybe it's already in there somewhere, I dunno. The basic info is there, but not in a table. That would come in quite handy... ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [GENERAL] wishlist: dynamic log volume control
Bruce Momjian <[EMAIL PROTECTED]> writes: > The issue is that you can't set log_connections from psql. Should we > improve the doc wording? I think the only thing missing is that in the introduction to section 16.4, where it says "The configuration file is reread whenever the postmaster process receives a SIGHUP signal", we should add something along the line of "Some parameters can only be set at server start; any changes to their entries in the configuration file will be ignored until the server is restarted". While a reasonable person could probably figure that out ;-) it would not hurt to say it explicitly. regards, tom lane ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [GENERAL] wishlist: dynamic log volume control
On Thursday February 19 2004 9:13, Bruce Momjian wrote: > > > > The 7.3.4 doc (doc/html/runtime-config.html) does say the > > log_connections option can only be set at server start or in the > > postgresql.conf configuration file. That seems a little ambiguous on > > the SIGHUP'ability of that option. My 7.3.4 install here shows all the > > log_* options are dynamically reloadable. > > The issue is that you can't set log_connections from psql. Should we > improve the doc wording? Ah, I had no idea that was the issue. Maybe a quick reference table in the docs would be helpful: Option SET option Reloads on SIGHUP = shared_buffers no no log_connectionsno yes log_statement yesyes ... Maybe it's already in there somewhere, I dunno. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
