Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: John Scalia <jayknowsunix@gmail.com>
Mime-Version: 1.0 (1.0)
Subject: Re: Maybe a possible bug in the partitioning code?
Date: Mon, 2 Nov 2020 11:38:19 -0500
Message-Id: <5F7F8C76-DA88-46D6-B0B6-DB9C84CE87C1@gmail.com>
References: <656221.1604334677@sss.pgh.pa.us>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
In-Reply-To: <656221.1604334677@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Precedence: bulk

Ok I also tried that Tom. Psql returned =E2=80=9CDid not find any relations n=
amed =E2=80=9C=E2=80=98.temp_my_table_global=E2=80=9D

Sent from my iPad

> On Nov 2, 2020, at 11:31 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>=20
> =EF=BB=BFJohn Scalia <jayknowsunix@gmail.com> writes:
>> While I=E2=80=99m waiting for my devs to confirm the first table that I p=
artitioned is working correctly, I started working on second of three that I=
 need to do. So, I added the code to end of my original script, but there wa=
s a typo in it. Now, as this code runs in a transaction block, so I don=E2=80=
=99t think anything it created should actually be present in the database, b=
ut on a subsequent rerunning, I got an error that one of the partition table=
s actually exists already. However, I cannot see it, nor drop it from the se=
rver. The error in the script is: relation =E2=80=9Ctemp_my_second_table_glo=
bal=E2=80=9D already exists, but the system cannot see it in order to drop i=
t, saying =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 m=
aybe drop it from there directly?
>=20
> Kinda sounds like a confusion over search_path, ie script is creating
> table in some schema that's not in your interactive search path?
>=20
> In psql, try
>   \d *.temp_my_second_table_global
> to see instances of temp_my_second_table_global in all schemas.
>=20
>            regards, tom lane