On Wed, 2025-02-19 at 16:49 +0100, Csányi Pál wrote:
> the trigger function definition is like:
> [...]
> INSERT INTO
> HAVONKENTI_MEGTAKARITASAINK (EZEN_IDOKOZBEN, MEGTAKARITVA_RSD, KELT)
> [...]
>
> and the trigger definition is like:
> CREATE OR REPLACE TRIGGER uj_nyugdij_beirasakor_kiold
>
On Wed, 19 Feb 2025 at 16:49, Csányi Pál wrote:
> Indeed I did, the trigger should have been assigned on
> javaink_forgalma table, not on havonkenti_megtakaritasaink table.
> Actually, this trigger has been assigned on both tables so far, and I
> just deleted it from the havonkenti_megtakaritasai
Sándor Daku ezt írta (időpont: 2025. febr.
19., Sze, 17:09):
>
>
>
> On Wed, 19 Feb 2025 at 16:49, Csányi Pál wrote:
>>
>> Indeed I did, the trigger should have been assigned on
>> javaink_forgalma table, not on havonkenti_megtakaritasaink table.
>> Actually, this trigger has been assigned on bot
a trigger function and a trigger which will run the
> > following code, see below.
> > Before this trigger would run, I tried this code.
> > When running the code I get the following error message:
> > ERROR: stack depth limit exceeded HINT: Increase the configuration
> >
Not related to the main question, but that query could use a little
adjustment. Something like:
WITH x AS (
select kelt from javaink_forgalma
where en_kaptam is true and az_aru_neve = 'nyugdíjam'
order by kelt desc limit 2
)
,y AS (select min(kelt) from x)
,z AS (select max(kelt) from x)
INS
gt; Before this trigger would run, I tried this code.
> When running the code I get the following error message:
> ERROR: stack depth limit exceeded HINT: Increase the configuration
> parameter "max_stack_depth" (currently 2048kB), after ensuring the
> platform's stack depth l
get the following error message:
ERROR: stack depth limit exceeded HINT: Increase the configuration
parameter "max_stack_depth" (currently 2048kB), after ensuring the
platform's stack depth limit is adequate.
Where am I making a mistake, and what can I do to make this code and
t
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
14 matches
Mail list logo