Re: Schema design: user account deletion vs. keeping family tree data - Mailing list pgsql-general

From Rob Sargent
Subject Re: Schema design: user account deletion vs. keeping family tree data
Date
Msg-id 20E42D70-9BE1-4CD9-B9A4-5E22EC73C791@gmail.com
Whole thread Raw
In response to Re: Schema design: user account deletion vs. keeping family tree data  (Bernice Southey <bernice.southey@gmail.com>)
List pgsql-general


On Nov 24, 2025, at 6:18 AM, Bernice Southey <bernice.southey@gmail.com> wrote:

Christoph Pieper <christoph@fecra.de> wrote:
Question:
From a PostgreSQL point of view (database best practices, data integrity, performance and long‑term maintainability at millions of rows), which approach would you prefer, or is there a better pattern for this kind of “account can be deleted, but genealogy should remain” use case?

I can tell you what I'm doing. It solved many design problems, but I
don't claim it's "best practice". I split my table in two.
   1 - columns that I can keep indefinitely
   2 - personal data
That way I just delete the personal data row when I want to remove it.

Thanks, Bernice



+1
Names are tricky, messy things.[1] Keep egoMaPa as leans as possible.


pgsql-general by date:

Previous
From: Dominique Devienne
Date:
Subject: Re: set role command
Next
From: immerrr again
Date:
Subject: DROP ROLE blocked by pg_init_privs