One issue is that these settings don't even exist in most builds unless
you add compiler flags.


Josh Berkus wrote:
> Jan,
> > No, not documenting it IS a good move.
> I couldn't disagree more.  Undocumented options?  Who are we, Microsoft?   
> >  If there's a button people will 
> > press it, if there's a switch people will turn it on and if there's a 
> > slot people will stick in whatever they have ... believe it or not, I 
> > have found a Xmas cookie in the floppy drive of a consultant's notebook 
> <snip>
> These kinds of people don't read the documentation in the first place, so 
> we're in no danger from them.
> I can definitely see an argument that the "developer" switches should be 
> documented on a different page of the docs from "Run-Time Configuration".  
> But the idea of having GUCs that aren't documented at all, anywhere, is a 
> very anti-Open Source idea.
> -- 
> -Josh Berkus
>  Aglio Database Solutions
>  San Francisco
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster

  Bruce Momjian                        |
  [EMAIL PROTECTED]               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
    (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

Reply via email to