From: Tom Lane <tgl@sss.pgh.pa.us>
To: John Scalia <jayknowsunix@gmail.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Maybe a possible bug in the partitioning code?
Date: Mon, 02 Nov 2020 11:31:17 -0500
Message-ID: <656221.1604334677@sss.pgh.pa.us> (raw)
In-Reply-To: <7135CF08-2B34-4B69-BFB5-FF57542478E1@gmail.com>
References: <7135CF08-2B34-4B69-BFB5-FF57542478E1@gmail.com>
John Scalia <jayknowsunix@gmail.com> writes:
> While I’m waiting for my devs to confirm the first table that I partitioned 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 was a typo in it. Now, as this code runs in a transaction block, so I don’t think anything it created should actually be present in the database, but on a subsequent rerunning, I got an error that one of the partition tables actually exists already. However, I cannot see it, nor drop it from the server. The error in the script is: relation “temp_my_second_table_global” already exists, but the system cannot see it in order to drop it, saying “temp_my_second_table_global” does not exist. That’s really a catch-22. Is there a system table where I can look and maybe drop it from there directly?
Kinda sounds like a confusion over search_path, ie script is creating
table in some schema that's not in your interactive search path?
In psql, try
\d *.temp_my_second_table_global
to see instances of temp_my_second_table_global in all schemas.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, jayknowsunix@gmail.com
Subject: Re: Maybe a possible bug in the partitioning code?
In-Reply-To: <656221.1604334677@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox