pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: gzh <gzhcoder@126.com>
To: pgsql-general@lists.postgresql.org
Subject: ERROR: stack depth limit exceeded
Date: Thu, 7 Sep 2023 15:45:06 +0800 (CST)
Message-ID: <1e6b9056.492e.18a6e9a1798.Coremail.gzhcoder@126.com> (raw)

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 the value of max_stack_depth can prevent code errors, 

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?




Regards




view thread (14+ messages)  latest in thread

Message-ID: <1e6b9056.492e.18a6e9a1798.Coremail.gzhcoder@126.com>
Permalink:  ../1e6b9056.492e.18a6e9a1798.Coremail.gzhcoder@126.com/
Also on:    postgresql.org/message-id/1e6b9056.492e.18a6e9a1798.Coremail.gzhcoder@126.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-general@postgresql.org
  Cc: gzhcoder@126.com, pgsql-general@lists.postgresql.org
  Subject: Re: ERROR: stack depth limit exceeded
  In-Reply-To: <1e6b9056.492e.18a6e9a1798.Coremail.gzhcoder@126.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox