From: | John Scalia <jayknowsunix(at)gmail(dot)com> |
---|---|
To: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Maybe a possible bug in the partitioning code? |
Date: | 2020-11-02 16:22:30 |
Message-ID: | 7135CF08-2B34-4B69-BFB5-FF57542478E1@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi all, again,
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?
—
Jay
Sent from my iPad
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-11-02 16:31:17 | Re: Maybe a possible bug in the partitioning code? |
Previous Message | John Scalia | 2020-11-02 15:38:39 | Re: More on my partitioning problem |