X-Original-To: pgsql-docs@postgresql.org Received: from localhost (developer.postgresql.org [64.117.224.193]) by developer.postgresql.org (Postfix) with ESMTP id E84549232D6 for ; Fri, 23 May 2003 11:46:03 -0400 (EDT) Received: from developer.postgresql.org ([64.117.224.193]) by localhost (developer.postgresql.org [64.117.224.193:10024]) (amavisd-new) with ESMTP id 70368-01 for ; Fri, 23 May 2003 11:45:51 -0400 (EDT) Received: from wolff.to (wolff.to [66.93.249.74]) by developer.postgresql.org (Postfix) with SMTP id 0A53D924EC8 for ; Fri, 23 May 2003 11:09:40 -0400 (EDT) Received: (qmail 4712 invoked by uid 500); 23 May 2003 15:11:39 -0000 Date: Fri, 23 May 2003 10:11:39 -0500 From: Bruno Wolff III To: pgsql-docs@postgresql.org Subject: GUC option ordering in 7.4 docs Message-ID: <20030523151139.GB3935@wolff.to> Mail-Followup-To: pgsql-docs@postgresql.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-new X-Archive-Number: 200305/11 X-Sequence-Number: 1781 While looking up statement_timeout in the 7.4 docs, I noticed that the GUC options seemed to be alphabetically ordered within a few groups. However, statement_timeout is not in the correct place if that scheme is being used. (It is between search_path and shared_buffers.)