| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | rootcause000(at)gmail(dot)com |
| Subject: | BUG #18159: Database Integrity Concerns: Missing FK Constraint |
| Date: | 2023-10-16 20:26:26 |
| Message-ID: | 18159-d47c6a6b62e40f00@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: 18159
Logged by: Root Cause
Email address: rootcause000(at)gmail(dot)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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Callahan, Drew | 2023-10-16 23:16:31 | Re: BUG #18155: Logical Apply Worker Timeout During TableSync Causes Either Stuckness or Data Loss |
| Previous Message | Tom Lane | 2023-10-16 15:46:54 | Re: Assert failure when CREATE TEMP TABLE |