MIME-Version: 1.0
References: <CAEzggP_UOGwe5BA9s3iLY3R8LEi4QztA=2ka+vkRp-Wy64vXdQ@mail.gmail.com>
In-Reply-To: <CAEzggP_UOGwe5BA9s3iLY3R8LEi4QztA=2ka+vkRp-Wy64vXdQ@mail.gmail.com>
From: Bernice Southey <bernice.southey@gmail.com>
Date: Mon, 24 Nov 2025 13:17:53 +0000
Message-ID: <CAEDh4nz_cKNGg0yX8k0yigZM8Ww=vcpv-0m_vMyR0je+5Kzm4Q@mail.gmail.com>
Subject: Re: Schema design: user account deletion vs. keeping family tree data
To: Christoph Pieper <christoph@fecra.de>
Cc: pgsql-general@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CAEDh4nz_cKNGg0yX8k0yigZM8Ww%3Dvcpv-0m_vMyR0je%2B5Kzm4Q%40mail.gmail.com>
Precedence: bulk

Christoph Pieper <christoph@fecra.de> wrote:
> Question:
> From a PostgreSQL point of view (database best practices, data integrity,=
 performance and long=E2=80=91term maintainability at millions of rows), wh=
ich approach would you prefer, or is there a better pattern for this kind o=
f =E2=80=9Caccount can be deleted, but genealogy should remain=E2=80=9D 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