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

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: yudara(at)respax(dot)com
Subject: BUG #18346: pg restore issue with generated cloumn in Postgres v13.14
Date: 2024-02-16 06:15:54
Message-ID: 18346-e72442085a58af97@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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:

We are having issue with restore some DBs to postgres v13.14 when there are
tables with "Generated Column (stored)".

Steps we did as follows
Back up a DB from pg_dump v13.14 from DB server(v13.14)
Restore using psql to same or another DB server(v13.14) . There is error
coming when creating a table which has a Generated Column (stored) saying
that relation does not exist(checking the existance of another table). This
generated column has a dependecy with another two tables which creates after
this table according the SQL command order in the dump file.

We do not get this error when restoring to the postgres version 13.12 ,
13.11 or below in the same major version.

So we suspect that it is something to do with the lastet postgres version
13.14. Can someone please assist ?

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message hubert depesz lubaczewski 2024-02-16 09:14:46 UPDATE modifies more rows that it should
Previous Message David Rowley 2024-02-16 02:56:31 Re: BUG #18344: Pruning tables partitioned by bool range fails with invalid strategy