Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nZGix-0000wZ-8f for pgsql-hackers@arkaria.postgresql.org; Tue, 29 Mar 2022 18:37:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nZGiv-0007rR-1e for pgsql-hackers@arkaria.postgresql.org; Tue, 29 Mar 2022 18:37:45 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nZGiu-0007rH-Ot for pgsql-hackers@lists.postgresql.org; Tue, 29 Mar 2022 18:37:44 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nZGio-0007oL-E4 for pgsql-hackers@lists.postgresql.org; Tue, 29 Mar 2022 18:37:43 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 22TIbVvh052605; Tue, 29 Mar 2022 14:37:31 -0400 From: Tom Lane To: Robert Haas cc: Andres Freund , Dilip Kumar , Ashutosh Sharma , Maciek Sakrejda , Bruce Momjian , Alvaro Herrera , Andrew Dunstan , Heikki Linnakangas , PostgreSQL Hackers Subject: Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints In-reply-to: References: <20220329173536.7d2ywdatsprxl4x6@alap3.anarazel.de> <48606.1648576426@sss.pgh.pa.us> <50701.1648577840@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Tue, 29 Mar 2022 14:24:40 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <52603.1648579051.1@sss.pgh.pa.us> Date: Tue, 29 Mar 2022 14:37:31 -0400 Message-ID: <52604.1648579051@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Robert Haas writes: > On Tue, Mar 29, 2022 at 2:17 PM Tom Lane wrote: >> it's some random algorithm that they probably feel at liberty >> to change. > I guess that characterization surprises me. The man page for > getopt_long() says this, and has for a long time at least on systems > I've used: Yeah, they say they follow the POSIX spec when you set POSIXLY_CORRECT. What they don't spell out in any detail is what they do when you don't. We know that it involves rearranging the argv[] array behind the application's back, but not what the rules are for doing that. In particular, they must have some undocumented and probably not very safe method for deciding which arguments are neither switches nor switch arguments. (Actually, if I recall previous discussions properly, another stumbling block to doing anything here is that we'd also have to change all our documentation to explain it. Fixing the command line synopses would be a mess already, and explaining the rules would be worse.) regards, tom lane