Re: How about a psql backslash command to show GUCs?

From: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Christoph Berg <myon(at)debian(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Joe Conway <mail(at)joeconway(dot)com>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, David Rowley <dgrowleyml(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: How about a psql backslash command to show GUCs?
Date: 2022-06-08 16:55:50
Message-ID: 8f498b02-f6a9-1544-4cb0-47dc2a5d3ae0@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 6/7/22 10:57 PM, Tom Lane wrote:
> "Jonathan S. Katz" <jkatz(at)postgresql(dot)org> 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.

Interesting. OK, I'd say let's keep the behavior that's in the patch.

Jonathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-06-08 17:26:50 Re: How about a psql backslash command to show GUCs?
Previous Message Robert Haas 2022-06-08 16:32:29 Re: replacing role-level NOINHERIT with a grant-level option