From: Tom Lane <tgl@sss.pgh.pa.us>
To: =?UTF-8?Q?Niklas_Hamb=C3=BCchen?= <mail@nh2.me>
cc: pgsql-bugs@lists.postgresql.org, ruben@benaco.com,
        =?UTF-8?Q?Niklas_Hamb=C3=BCchen?= <niklas@benaco.com>
Subject: Re: "memory exhausted" in query parser/simplifier for many nested
 parentheses
In-reply-to: <161892c0-65fc-42a6-8af9-b098879decd4@nh2.me>
References: <161892c0-65fc-42a6-8af9-b098879decd4@nh2.me>
Comments: In-reply-to =?UTF-8?Q?Niklas_Hamb=C3=BCchen?= <mail@nh2.me>
	message dated "Wed, 11 Dec 2024 22:59:41 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <654488.1734019548.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 12 Dec 2024 11:05:48 -0500
Message-ID: <654489.1734019548@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/654489.1734019548%40sss.pgh.pa.us>
Precedence: bulk

=3D?UTF-8?Q?Niklas_Hamb=3DC3=3DBCchen?=3D <mail@nh2.me> writes:
> we noticed that when writing a large query of form
>     (((A OR B) OR C) OR ...)
> with many terms (e.g. 13000) this causes one of two errors:
> 1. memory exhausted at or near "("
> 2. stack depth limit exceeded
> ...
> We consider this a bug because it means one cannot easily generate large=
 queries that query a couple thousand entries in a `SELECT ... WHERE` cond=
ition.

[ shrug... ]  Even if these examples didn't fail, they would perform
terribly.  Limits are a fact of life.  Write your query some other
way, for example using "x IN (list)" or other shortcut syntaxes.

			regards, tom lane