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 1nyltS-0007NV-2y for pgsql-hackers@arkaria.postgresql.org; Wed, 08 Jun 2022 02:58:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nyltP-0000RR-CI for pgsql-hackers@arkaria.postgresql.org; Wed, 08 Jun 2022 02:57:59 +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 1nyltO-0000QA-Ux for pgsql-hackers@lists.postgresql.org; Wed, 08 Jun 2022 02:57:58 +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 1nyltG-0008UW-QA; Wed, 08 Jun 2022 02:57:54 +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 2582vbeO1478412; Tue, 7 Jun 2022 22:57:37 -0400 From: Tom Lane To: "Jonathan S. Katz" cc: Christoph Berg , Robert Haas , Justin Pryzby , Julien Rouhaud , Pavel Stehule , "David G. Johnston" , Joe Conway , Mark Dilger , Andrew Dunstan , David Rowley , Alvaro Herrera , PostgreSQL Hackers Subject: Re: How about a psql backslash command to show GUCs? In-reply-to: <47102fd4-f2c9-40c3-f6dc-0f99d6b6ed6f@postgresql.org> References: <9439380b-a81f-c910-f527-db4d470b026b@postgresql.org> <531275.1649707882@sss.pgh.pa.us> <7bba5a32-65fe-04e1-7c36-efd963a625c9@postgresql.org> <807242.1649776780@sss.pgh.pa.us> <20220606135529.GV29853@telsasoft.com> <918042.1654531335@sss.pgh.pa.us> <952350.1654549308@sss.pgh.pa.us> <29d873fa-ce53-0eeb-ddf5-0a0d38458d16@postgresql.org> <1219250.1654621343@sss.pgh.pa.us> <1436476.1654646305@sss.pgh.pa.us> <47102fd4-f2c9-40c3-f6dc-0f99d6b6ed6f@postgresql.org> Comments: In-reply-to "Jonathan S. Katz" message dated "Tue, 07 Jun 2022 20:35:50 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1478410.1654657057.1@sss.pgh.pa.us> Date: Tue, 07 Jun 2022 22:57:37 -0400 Message-ID: <1478411.1654657057@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "Jonathan S. Katz" writes: > I don't know how frequently issues around "max_stack_depth" being too > small are reported -- I'd be curious to know that -- but I don't have > any strong arguments against allowing the behavior you describe based on > our current docs. I can't recall any recent gripes on our own lists, but the issue was top-of-mind for me after discovering that NetBSD defaults "ulimit -s" to 2MB on at least some platforms. That would leave us setting max_stack_depth to something less than that, probably about 1.5MB. regards, tom lane