pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18159: Database Integrity Concerns: Missing FK Constraint
2+ messages / 2 participants
[nested] [flat]
* BUG #18159: Database Integrity Concerns: Missing FK Constraint
@ 2023-10-16 20:26 PG Bug reporting form <noreply@postgresql.org>
2023-10-17 01:09 ` Re: BUG #18159: Database Integrity Concerns: Missing FK Constraint Laurenz Albe <laurenz.albe@cybertec.at>
0 siblings, 1 reply; 2+ messages in thread
From: PG Bug reporting form @ 2023-10-16 20:26 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: rootcause000@gmail.com
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?
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: BUG #18159: Database Integrity Concerns: Missing FK Constraint
2023-10-16 20:26 BUG #18159: Database Integrity Concerns: Missing FK Constraint PG Bug reporting form <noreply@postgresql.org>
@ 2023-10-17 01:09 ` Laurenz Albe <laurenz.albe@cybertec.at>
0 siblings, 0 replies; 2+ messages in thread
From: Laurenz Albe @ 2023-10-17 01:09 UTC (permalink / raw)
To: rootcause000@gmail.com; pgsql-bugs@lists.postgresql.org
On Mon, 2023-10-16 at 20:26 +0000, PG Bug reporting form wrote:
> Is there a possibility that during the vacuum process, FK constraints might
> be dropped and recreated for restructuring?
No, that cannot happen.
You must have lost your foreign key constraints some other way (somebody ran
ALTER TABLE). There is no indication that this is a PostgreSQL bug.
Yours,
Laurenz Albe
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2023-10-17 01:09 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-10-16 20:26 BUG #18159: Database Integrity Concerns: Missing FK Constraint PG Bug reporting form <noreply@postgresql.org>
2023-10-17 01:09 ` Laurenz Albe <laurenz.albe@cybertec.at>
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