From: | Erik Wienhold <ewie(at)ewie(dot)name> |
---|---|
To: | Florian Koch <florian(dot)murat(dot)koch(at)gmail(dot)com> |
Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: I get ERROR: column "table_name" does not exist |
Date: | 2024-06-07 01:24:19 |
Message-ID: | f1d6eec7-1b52-4103-944b-b633b56d34a8@ewie.name |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On 2024-06-06 15:08 +0200, Florian Koch wrote:
> This is the working example, when I replace any of e.g.
> 'PG_EXCEPTION_HINT' with 'TABLE_NAME'. Then the function throws. I am
> using postgres 16.1.
Perhaps you did not declare variable table_name and run something like:
RETURN jsonb_build_object('table', table_name);
But that's still guesswork without seeing the actual function definition
with your edits.
> On Wed, Jun 5, 2024 at 6:32 PM Erik Wienhold <ewie(at)ewie(dot)name> wrote:
> >
> > 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
From | Date | Subject | |
---|---|---|---|
Next Message | PG Doc comments form | 2024-06-07 03:46:27 | CLUSTER details |
Previous Message | Florian Koch | 2024-06-06 13:08:59 | Re: I get ERROR: column "table_name" does not exist |