Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tkmdS-006lja-6U for pgsql-general@arkaria.postgresql.org; Wed, 19 Feb 2025 16:09:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tkmdQ-00AaKe-Lr for pgsql-general@arkaria.postgresql.org; Wed, 19 Feb 2025 16:09:16 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tkmdQ-00AaKV-AM for pgsql-general@lists.postgresql.org; Wed, 19 Feb 2025 16:09:16 +0000 Received: from mail-lj1-x235.google.com ([2a00:1450:4864:20::235]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tkmdO-001jrJ-24 for pgsql-general@lists.postgresql.org; Wed, 19 Feb 2025 16:09:15 +0000 Received: by mail-lj1-x235.google.com with SMTP id 38308e7fff4ca-30738a717ffso62688361fa.0 for ; Wed, 19 Feb 2025 08:09:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1739981353; x=1740586153; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=20O/rQvs0Oo3r/8pnvIQnT9v+rGrWaBoeBUy1CJrbKo=; b=PucJgKm5WyES49v9j5VbaOYZHQKmyWUQI0rhl2zvpRPeqEQda4N5iCGwXBJ0uQuddB s2ZRU4JFfR6pLm6Tl5vytVmHgs9Mp9wnyt9x2aijbJLP8IYm561pRtxfpJbPgco2UZcJ uUx/ypx2XWV7mq0XVRLQthsjQ2YbsM4Z4+pK959mAvT4QCHUXrJmgEPcRhidt+SNrLPA 8ss02vXGMIMUt9bBsxz5Vxmzfo1bFAtpDykYqgAAigTiOIFMUvByjM9yvedjZJpcJuf6 LwlEr+E+weKBsnBAvtwqIAaFSIzGyaefrzmlFBkNFRknMSAvuC0O332p0i7uCuC+QG19 9Aog== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1739981353; x=1740586153; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=20O/rQvs0Oo3r/8pnvIQnT9v+rGrWaBoeBUy1CJrbKo=; b=ZkVk0CZgEtYxAymBoiaF8SGEne0gODVokYbDvaWvDKg/Wv6JR0ygXte0xYUCFnFRg9 5vGBb2jESk8F6yuNRQFk2IyW/7N/CPJK7uZ5Yr3w9ttzaJMJkZHYk2d5FmR+k5OxwgkY i0JCnIhN2VGlGyffEU8svwdAD8ViKuYME3Hm6s4P8MnlETsbp7XaQ6XLpxC1j+hd3TTN H6ckfVH9GKDNH60NDwSI4byKU9X+hotE7LHpWlcz+z7gCCMQk+XtPcvY2paZSmvkcRLs mfd7X9U2Ww5DaWjjchiX5kNldadlAp+wTvWhqutv+jNmTfhdtOfRTWpa7272uFAcQ0sZ Tmyw== X-Gm-Message-State: AOJu0Yx0o+A6EQHUgzjUlHK0YwWGW0rnoVezxdwhi1MpdsDg7p96wdCF fNGBNNn8ppgPWmqJ8LQzkkSVnh8cN50dnEGCiyBO06PURuSiDT7wKavvJ/KC/C8bajiWGpFx4OF eSXKb0YGI+MuieSe4DunG9FwaS+g= X-Gm-Gg: ASbGncscozy3he8fX+E0DZEJ+oRszRLwrPcO3UC/kU2+9SKZ5WY5Oo928MVlzB4Oqs5 B0OnVrPCBxTZen1dLQ9x8WEcnYdm+t7DqS8gNz9Xhs69SZLnVa6bceitFEZ86ytLEZfVvvetHLg == X-Google-Smtp-Source: AGHT+IEfCtySToAfd11VxP3z6fALCdoqnD+KSmd1NKM2ZVqLI0Jiv+lGcneVWtlhuO9u3Wb3hgxS39bgKEx2cSf9WjM= X-Received: by 2002:a05:6512:3e1e:b0:545:285e:7777 with SMTP id 2adb3069b0e04-5452fe8be85mr6926047e87.39.1739981352778; Wed, 19 Feb 2025 08:09:12 -0800 (PST) MIME-Version: 1.0 References: <2b9a5afa4abfcdbab0a585c1a77279dc90a60a83.camel@cybertec.at> In-Reply-To: From: =?UTF-8?B?U8OhbmRvciBEYWt1?= Date: Wed, 19 Feb 2025 17:09:01 +0100 X-Gm-Features: AWEUYZm9E-G80bJ4hAKkpI3kweWbf270fZffH36mPCMfmYS44N2CYeObw4Eezd0 Message-ID: Subject: Re: ERROR: stack depth limit exceeded To: csanyipal@gmail.com Cc: general pgsql Content-Type: multipart/alternative; boundary="00000000000072c586062e80fa5a" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000072c586062e80fa5a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, 19 Feb 2025 at 16:49, Cs=C3=A1nyi P=C3=A1l wr= ote: > 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=C3=A1l, 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=C3=A1ndor --00000000000072c586062e80fa5a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Wed, 19 Feb = 2025 at 16:49, Cs=C3=A1nyi P=C3=A1l <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=C3= =A1l,

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=C2=A0to see here.
Before= that the trigger activating on insert into havonkenti_megtakaritasaink ins= erted a record into havonkenti_megtakaritasaink which activated the trigger= again and this continued until it ran into the max_stack_depth wall.
=

Regards,
S=C3=A1ndor
--00000000000072c586062e80fa5a--