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 11:22:30 -0500
Subject: Maybe a possible bug in the partitioning code?
Message-Id: <7135CF08-2B34-4B69-BFB5-FF57542478E1@gmail.com>
To: pgsql-admin <pgsql-admin@postgresql.org>
Precedence: bulk

Hi all, again,

While I=E2=80=99m waiting for my devs to confirm the first table that I part=
itioned is working correctly, I started working on second of three that I ne=
ed to do. So, I added the code to end of my original script, but there was a=
 typo in it. Now, as this code runs in a transaction block, so I don=E2=80=99=
t think anything it created should actually be present in the database, but o=
n a subsequent rerunning, I got an error that one of the partition tables ac=
tually exists already. However, I cannot see it, nor drop it from the server=
. The error in the script is: relation =E2=80=9Ctemp_my_second_table_global=E2=
=80=9D already exists, but the system cannot see it in order to drop it, say=
ing =E2=80=9Ctemp_my_second_table_global=E2=80=9D does not exist. That=E2=80=
=99s really a catch-22. Is there a system table where I can look and maybe d=
rop it from there directly?
=E2=80=94
Jay

Sent from my iPad=