Thank you all for taking the time to help me with my question and offer your
advice. Your responses were greatly appreciated!
At 2023-09-08 21:53:33, "Tom Lane" wrote:
>gzh writes:
>> In the Release Notes for PostgreSQL 12.14, we saw the following change:
>> https://www.postgre
gzh writes:
> In the Release Notes for PostgreSQL 12.14, we saw the following change:
> https://www.postgresql.org/docs/release/12.14/
>> Add recursion and looping defenses in subquery pullup (Tom Lane)
>> A contrived query can result in deep recursion and unreasonable amounts of
>> time spent
On Fri, 2023-09-08 at 11:32 +0800, gzh wrote:
> I'm sorry I didn't explain the issue clearly.
> Our system is currently running on PostgreSQL 12.13 and we are planning to
> upgrade to PostgreSQL 12.16.
> We are currently in the evaluation phase.
> In the Release Notes for PostgreSQL 12.14, we s
to 12.16.
>> If multiple subqueries or a large number of UNION ALL were used,
>> the previously unseen error message "ERROR: stack depth limit exceeded" will
>> appear after upgrading the version.
>
>Please provide a self-contained example. The peop
On Thu, 7 Sept 2023 at 08:45, gzh wrote:
> but is there a good way to find out which SQL statements have issues without
> having to run all SQL statements, as it would be too expensive?
Does your postgresql server log not contain the error with the
statement at issue?
Geoff
gzh writes:
> I upgraded the version of PostgreSQL from 12.13 to 12.16.
> If multiple subqueries or a large number of UNION ALL were used,
> the previously unseen error message "ERROR: stack depth limit exceeded" will
> appear after upgrading the version.
Please pr
Hi,
I upgraded the version of PostgreSQL from 12.13 to 12.16.
If multiple subqueries or a large number of UNION ALL were used,
the previously unseen error message "ERROR: stack depth limit exceeded" will
appear after upgrading the version.
I understand that increasing th
