From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: rootcause000@gmail.com
Subject: BUG #18159: Database Integrity Concerns: Missing FK Constraint
Date: Mon, 16 Oct 2023 20:26:26 +0000
Message-ID: <18159-d47c6a6b62e40f00@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 18159
Logged by: Root Cause
Email address: rootcause000@gmail.com
PostgreSQL version: Unsupported/Unknown
Operating system: Windows
Description:
Version - PostgreSQL 10.21, compiled by Visual C++ build 1800, 64-bit
We are currently experiencing issues in the database where foreign key (FK)
constraints are missing, leading to orphaned rows. Upon investigation, we
suspect that we are currently running a vacuum on tables according to a
schedule, and also as a standalone process when the product is not
running.
Is there a possibility that during the vacuum process, FK constraints might
be dropped and recreated for restructuring? If so, are there any chances
that they will not be recreated?
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: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, rootcause000@gmail.com
Subject: Re: BUG #18159: Database Integrity Concerns: Missing FK Constraint
In-Reply-To: <18159-d47c6a6b62e40f00@postgresql.org>
* 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