Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kdeLl-0008WB-DP for pgsql-bugs@arkaria.postgresql.org; Fri, 13 Nov 2020 19:03:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kdeLk-0005pP-1j for pgsql-bugs@arkaria.postgresql.org; Fri, 13 Nov 2020 19:03:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kdeLj-0005pI-Rl for pgsql-bugs@lists.postgresql.org; Fri, 13 Nov 2020 19:03:07 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kdeLh-0007n2-JV for pgsql-bugs@lists.postgresql.org; Fri, 13 Nov 2020 19:03:07 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 0ADJ33fm393737; Fri, 13 Nov 2020 14:03:03 -0500 From: Tom Lane To: emmanuel.ona@seetickets.fr cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16717: ERRORDATA_STACK_SIZE exceeded after 5 times of the same command In-reply-to: <16717-990bd4d9bb55acab@postgresql.org> References: <16717-990bd4d9bb55acab@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Fri, 13 Nov 2020 18:14:26 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <393735.1605294183.1@sss.pgh.pa.us> Date: Fri, 13 Nov 2020 14:03:03 -0500 Message-ID: <393736.1605294183@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form writes: > this behaviour drives me crazy, using a data wrapper (mysql_fdw) from a > mariadb instance to initialize a postgres foreign table, i'm facing the > following issue after running the fifth's time the same "import foreign > schema..." command. Can't reproduce any such thing with postgres_fdw, so I suppose this is a bug in mysql_fdw, not IMPORT FOREIGN SCHEMA generally. It is probably dealing with some situation by catching an error, and then forgetting to clean up after itself (with FlushErrorState). I'd suggest reporting this to whatever the contact address for mysql_fdw is. regards, tom lane