Re: [HACKERS] Proposal for Re-ordering CONF (was: Re: GUC and postgresql.conf docs)

2003-06-03 Thread Josh Berkus
Tom, > Josh's proposal looks pretty good to me in general, though some of the > details seem a little odd. "max_files_per_process" doesn't belong under > lock management (perhaps better to stick it under Memory Usage, possibly > renaming that category to Resource Consumption) and the Query Tuning

Re: [HACKERS] Proposal for Re-ordering CONF (was: Re: GUC and postgresql.conf docs)

2003-06-03 Thread Tom Lane
Bruce Momjian <[EMAIL PROTECTED]> writes: > Agreed, postgresql.conf and the documentation should match. Guc.c needs > to be in variable _type_ order, so I don't know what can be done > there. We could make each table in guc.c follow the logical ordering Josh suggests for its subset of the variabl

Re: [HACKERS] Proposal for Re-ordering CONF (was: Re: GUC and postgresql.conf docs)

2003-06-03 Thread Josh Berkus
Bruce, > I don't think people change _that_ _many_ postgresql.conf settings, so > reordering should be OK with them, especially if they get a clearer > output. Yeah. I put in the objection because Elein already made it to me. I also think that most people don't adjust *enough* Postgresql.conf s

[HACKERS] Proposal for Re-ordering CONF (was: Re: GUC and postgresql.conf docs)

2003-06-03 Thread Josh Berkus
Bruce, > I have developed the following patch to address these issues. I have > removed the lock GUC settings from postgresql.conf, as suggested. (They > aren't even enabled in the general builds.) Great! Just to keep you from getting complacent, what follows is a proposal for re-ordering th