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 1tkmi5-006mH8-KU for pgsql-general@arkaria.postgresql.org; Wed, 19 Feb 2025 16:14:05 +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 1tkmi3-00Ahsk-UA for pgsql-general@arkaria.postgresql.org; Wed, 19 Feb 2025 16:14:04 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tkmi3-00Ahsb-JG for pgsql-general@lists.postgresql.org; Wed, 19 Feb 2025 16:14:03 +0000 Received: from mail-wm1-x329.google.com ([2a00:1450:4864:20::329]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tkmi1-001n7x-1h for pgsql-general@lists.postgresql.org; Wed, 19 Feb 2025 16:14:03 +0000 Received: by mail-wm1-x329.google.com with SMTP id 5b1f17b1804b1-4399a1eada3so10977745e9.2 for ; Wed, 19 Feb 2025 08:14:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1739981640; x=1740586440; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :reply-to:in-reply-to:references:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=rwUEncDjf1m7yizw/PQZFOvwjgqx4hY2lmFAdvwPRW0=; b=DVOq+4Me/eQR8Y3rF3pQVwJuwpjTbiE0ED/vKFOdIlgZ8Uh3FW3DMJ7q816NjxF8wI BObX9+Ioyqbet7JU3tbH9ZOIeXeO3YS2yIzEa+azBkur4jYacCxrvy/Q6old0/ozh/KS Wc62Lld7rYEop7lg6ENFbzFsRU5EqxXOHRlkFq/bXWXYAvSO4Ux/GMsvRbnwzqRkI5Xm N8RO5l3JlqXeBbD4XWx7ON4iv5Bh1WjIiUDQhZ1ycoHLmBwkuV0B3COo5SXPz8Akudzw 6ZkXfdhcQtohC5z9TBXiIj491MZnjbE6thbf9YLuMWsnmM/3Sj7Cp+IeH2O617JhlZJd lAig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1739981640; x=1740586440; h=content-transfer-encoding:cc:to:subject:message-id:date:from :reply-to:in-reply-to:references:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=rwUEncDjf1m7yizw/PQZFOvwjgqx4hY2lmFAdvwPRW0=; b=X7KjqILKTqzqsuCYJ1Z5XQMjvj5U7c+QlWSJetOeK20+HAazYSrZ4RysNqymit/CQ8 asWHMbweIO6HcsS0A/BD0IcC4ethKbvnKKDPpnF3vVf6uf79LVSgDdG6Rnuc4v8WFp4J yjWFYp25waBmqX3YwHvjc1pdSpJGF/Bb7oYvMIhJihKD1HfUUF8Padw5hiI2LutrFwrk wnirT8LpoAYIvszBE5hOEbSp8lvBVFArRG6gtszhqdbcBcBty2jePW6tuAzhdliYm1MO QTrnTDiRpShDx+NuQ6R7onqPsOfnuscMzcUJxXXZqlagU6EyZqIUhUJ3wuZsyqgzgyvl p/DQ== X-Gm-Message-State: AOJu0YwuCDQKZe5/LD2PUcv1L6ZajwLyH39v8cMmSpN1er4Adg8h19dz YagoRlulFvkvEtdchnEEjGlXmhvDmQbqskBhiCmg8d/8luGnV9B05OfMEQQzdVHUDaKFILHB7/0 9kTR9z9cNAxJZVKfLzgw3SiXIAfQ= X-Gm-Gg: ASbGnctYBABJf/tVNJDuHLNdMRUTpoh3g3MZXPe2X29cCw6Xv5ezspaKGTpZdUHFC7c ojMEvoILC30fj4vHtOexukgQmq0idK8ahbb9WRFPRyTK9FpU5nahmdSKQeIGfvbnJHmnx2ig7 X-Google-Smtp-Source: AGHT+IGQBQTaXjVsu3YgFtH1RyanK918nFkkTfRfumZzNO8FL5Bqb/4YlVfCzArF4IZsT/xGYvSVY6XdoQ7XSwgDoeU= X-Received: by 2002:a05:600c:1c86:b0:439:88bb:d000 with SMTP id 5b1f17b1804b1-43999dd981bmr36530095e9.25.1739981640516; Wed, 19 Feb 2025 08:14:00 -0800 (PST) MIME-Version: 1.0 References: <2b9a5afa4abfcdbab0a585c1a77279dc90a60a83.camel@cybertec.at> In-Reply-To: Reply-To: csanyipal@gmail.com From: =?UTF-8?B?Q3PDoW55aSBQw6Fs?= Date: Wed, 19 Feb 2025 17:13:48 +0100 X-Gm-Features: AWEUYZkqvMtH544I9zPCXI4O182cd8G1ptqGlvJJBCFsUxo2hIBZcIYCaF5Nbzo Message-ID: Subject: Re: ERROR: stack depth limit exceeded To: =?UTF-8?B?U8OhbmRvciBEYWt1?= Cc: general pgsql Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk S=C3=A1ndor Daku ezt =C3=ADrta (id=C5=91pont: 2025.= febr. 19., Sze, 17:09): > > > > On Wed, 19 Feb 2025 at 16:49, Cs=C3=A1nyi P=C3=A1l = 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 snippe= t works now after deleting the trigger on havonkenti_megtakaritasaink then = nothing to see here. > Before that the trigger activating on insert into havonkenti_megtakaritas= aink inserted a record into havonkenti_megtakaritasaink which activated the= trigger again and this continued until it ran into the max_stack_depth wal= l. > > Regards, > S=C3=A1ndor Hi S=C3=A1ndor, Thank you very much to you and everyone else who helped me solve this probl= em! --=20 Best wishes by Paul Chanyi!