Message-ID: <cbad2d1e795179b28ef82d021839ef15e56db93c.camel@cybertec.at>
Subject: Re: Partition table with a foreign key self-reference
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Oliver Urones <ourones.joinup@gmail.com>,
	pgsql-admin@lists.postgresql.org
Date: Wed, 05 Feb 2025 08:18:02 +0100
In-Reply-To: 
 <CAH2eNKX7wg7mZYr6jt4c6iZey6HYQUY-3DLPJMT3wWqy1gNFmg@mail.gmail.com>
References: 
	<CAH2eNKX7wg7mZYr6jt4c6iZey6HYQUY-3DLPJMT3wWqy1gNFmg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.54.3 (3.54.3-1.fc41) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/cbad2d1e795179b28ef82d021839ef15e56db93c.camel%40cybertec.at>
Precedence: bulk

On Tue, 2025-02-04 at 16:57 +0100, Oliver Urones wrote:
> I need help with the process of partitioning tables.
>=20
> How can I partition a table that has a foreign key that references itself=
?
>=20
> Something like this example:
>=20
> CREATE TABLE employees (
> =C2=A0 =C2=A0 employee_id SERIAL PRIMARY KEY,
> =C2=A0 =C2=A0 name VARCHAR(50),
> =C2=A0 =C2=A0 boss_id INTEGER,
> =C2=A0 =C2=A0 CONSTRAINT fk_boss FOREIGN KEY (boss_id) REFERENCES employe=
es(employee_id)
> );
>=20
> I'm using Postgresql 14.

The question makes no sense as such.  You'd have to tell us the purpose
you want to achieve with partitioning.  Depending on that, you'd choose
the partitioning strategy and the partitioning key.

At any rate, you'll probably have to drop the foreign key constraint
unless your partitioning key is "id".

Yours,
Laurenz Albe