Re: ERROR: stack depth limit exceeded - Mailing list pgsql-general

From Sándor Daku
Subject Re: ERROR: stack depth limit exceeded
Date
Msg-id CAKyoTgbn_sdCZig9G9vjCXtMHeO0M8W=nHsrR_-bfjrHuRY1rA@mail.gmail.com
Whole thread Raw
In response to Re: ERROR: stack depth limit exceeded  (Csányi Pál <csanyipal@gmail.com>)
Responses Re: ERROR: stack depth limit exceeded
List pgsql-general


On Wed, 19 Feb 2025 at 16:49, Csányi Pál <csanyipal@gmail.com> 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_megtakaritasaink table by using
PgAdmin4.

Now that I only have this trigger assigned on the javaink_forgalma
table, an INSERT command into this table will activate the trigger
function, which will then insert a new row in the
havonkenti_megtakaritasaink table.

However, by copying the code between BEGIN and END from the trigger
function, and inserting it into the Query tool and then running this
code there, it should insert a line in the havonkenti_megtakaritasaink
table.

But here I got the error message mentioned above. Hey! But now this
code snippet ran without any errors! So what happened here?

Thanks for all the advice!

--
Best wishes by Paul Chanyi!


Hi Pál,

I'm not sure that I follow the timeline correctly, but if the code snippet works now after deleting the trigger on havonkenti_megtakaritasaink then nothing to see here.
Before that the trigger activating on insert into havonkenti_megtakaritasaink inserted a record into havonkenti_megtakaritasaink which activated the trigger again and this continued until it ran into the max_stack_depth wall.

Regards,
Sándor

pgsql-general by date:

Previous
From: Csányi Pál
Date:
Subject: Re: ERROR: stack depth limit exceeded
Next
From: Adrian Klaver
Date:
Subject: Re: AW: PGDG PostgreSQL Debian package: Question on conditions for creation of new cluster