Re: BUG #18346: pg restore issue with generated cloumn in Postgres v13.14

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: "yudara(at)respax(dot)com" <yudara(at)respax(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #18346: pg restore issue with generated cloumn in Postgres v13.14
Date: 2024-02-16 11:20:15
Message-ID: CAKFQuwbGTHbhqahhW+3_Ej9aY9PKtav-i0XL3Q4pD_+bCAxOSQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thursday, February 15, 2024, PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:

> The following bug has been logged on the website:
>
> Bug reference: 18346
> Logged by: YG
> Email address: yudara(at)respax(dot)com
> PostgreSQL version: 13.14
> Operating system: Ubuntu-20.04.2
> Description:
>
> This
> generated column has a dependecy with another two tables which creates
> after
> this table according the SQL command order in the dump file.
>

These dependencies are not allowed. Change your generated expression to a
trigger.

David J.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message David Rowley 2024-02-16 11:25:28 Re: UPDATE modifies more rows that it should
Previous Message David Rowley 2024-02-16 11:16:33 Re: UPDATE modifies more rows that it should