Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: John Scalia <jayknowsunix@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Mon, 2 Nov 2020 07:40:26 -0500
Subject: More on my partitioning problem
Message-Id: <A74FFBFA-14BE-4FEB-9B0C-AD3AA056BF5C@gmail.com>
To: pgsql-admin <pgsql-admin@postgresql.org>
Precedence: bulk

Hi guys, again,

Laurenz=E2=80=99s suggestion to use create table like including all did not w=
ork, due to the fact that the partitioning key is not part of the original b=
ase table=E2=80=99s primary key. I had also forgotten about using the LIKE c=
onstruct. So, thanks Laurenz, but this also means I cannot use INCLUDING IND=
EXES, so I have to recreate all the indexes again on the new partitioned bas=
e table,, but I=E2=80=99m having an issue with the new table=E2=80=99s prima=
ry key.

I created a UNIQUE INDEX on the new base table using the original primary ke=
y and the partitioning key. So far, so good. But doing an ALTER TABLE ADD PR=
IMARY KEY USING INDEX, is not supported. So. being that  I already have a un=
ique index here, does it really matter if I do not declare a primary key her=
e? Otherwise, how would I go about creating a primary key on this partitione=
d table?
=E2=80=94
Jay
Sent from my iPad=