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 1sEtYi-004RkK-Kl for pgsql-docs@arkaria.postgresql.org; Wed, 05 Jun 2024 16:32:22 +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 1sEtYi-009kJ7-Fd for pgsql-docs@arkaria.postgresql.org; Wed, 05 Jun 2024 16:32:20 +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 1sEtYh-009kHr-7m for pgsql-docs@lists.postgresql.org; Wed, 05 Jun 2024 16:32:20 +0000 Received: from mout-u-204.mailbox.org ([80.241.59.204]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sEtYd-003baZ-VW for pgsql-docs@lists.postgresql.org; Wed, 05 Jun 2024 16:32:18 +0000 Received: from smtp102.mailbox.org (smtp102.mailbox.org [IPv6:2001:67c:2050:b231:465::102]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-u-204.mailbox.org (Postfix) with ESMTPS id 4VvXzp5G8kz9sc1; Wed, 5 Jun 2024 18:32:06 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ewie.name; s=MBO0001; t=1717605126; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=3gjKFAClX5lF9esK6q7y/xKeOMjVa9LVLLyaM2qXyL8=; b=xmc1oUNuWmskGAmpFtH8quwIzzl6sX8TyxzJk/3qFqzEs9YY4jLEEwQ/7n9i4eAm4q97Kr cjmVnf0r235dxN6IrdGPtGZFfS8/8R6WajTmHOqWkOF7zhxswMasQduckvq5pAf1O4T/1V OsOnj+nx85vpq4GfZw252ScEba2u3GvLVsbJq/Tx821cSHxBDLLFn1qcAThaYvBiY5ZdU8 eK9/ANRGh61IHuEC7lP2vpyLRWdvf6ieMN2ivdlznnmfMOtoNdMcJSzlk8gH2/QsQeMydv UMqjQyeJmnsocOsYEsPKW/SNl5EEtx+EmhUXjWdQ5bG4mG14MsrEIfjsB4HLIA== Date: Wed, 5 Jun 2024 18:32:04 +0200 From: Erik Wienhold To: florian.murat.koch@gmail.com, pgsql-docs@lists.postgresql.org Subject: Re: I get ERROR: column "table_name" does not exist Message-ID: <26d7c4dd-2809-426a-acb4-bbd2828fba93@ewie.name> References: <171753061515.2021730.14624637049210791754@wrigleys.postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <171753061515.2021730.14624637049210791754@wrigleys.postgresql.org> X-Rspamd-Queue-Id: 4VvXzp5G8kz9sc1 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2024-06-04 21:50 +0200, PG Doc comments form wrote: > When using GET STACKED DIAGNOSTICS in PL/pgSQL accessing TABLE_NAME, > COLUMN_NAME, CONSTRAINT_NAME or SCHEMA_NAME throws an error. > > The function "shared.test_raise_exception": > https://github.com/rin-nas/postgresql-patterns-library/issues/8#issuecomment-2147984520 * Do you have a reproducer with those diagnostic items? The linked script does not use any of the items that you've mentioned. * Which Postgres version? -- Erik