From: Tomas Vondra <tomas.vondra@enterprisedb.com>
To: zhxpgh <zhxpgh@foxmail.com>
To: pgsql-bugs <pgsql-bugs@lists.postgresql.org>
Subject: Re: two bugs
Date: Sat, 25 Feb 2023 14:37:39 +0100
Message-ID: <5dfefe9d-c03b-d831-2a16-8baa61d18b46@enterprisedb.com> (raw)
In-Reply-To: <tencent_7294503D958856DB8D18599B2CF2C0AA4406@qq.com>
References: <tencent_7294503D958856DB8D18599B2CF2C0AA4406@qq.com>
I don't think any of this a bug, it's the expected behavior. It would be
better if you also shared some reasoning why you think these are bugs.
1) DISABLE TRIGGER ALL disables all triggers, including those for
referential integrity. So it's not surprising some of the data violates
the FK on restore.
2) Similarly for the materialized view - you create a unique index on
the MV at a point when there's no duplicates. But then you insert data
into the source tables. If you tried to refresh the MV at this point,
it'd fail - which is expected. And restore first loads all the data and
then builds the materialized view. We don't have the capability to
dump/restore the MV data directly, we have to run the query.
regards
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tomas.vondra@enterprisedb.com, zhxpgh@foxmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: two bugs
In-Reply-To: <5dfefe9d-c03b-d831-2a16-8baa61d18b46@enterprisedb.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox