From: | John Scalia <jayknowsunix(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Maybe a possible bug in the partitioning code? |
Date: | 2020-11-02 16:38:19 |
Message-ID: | 5F7F8C76-DA88-46D6-B0B6-DB9C84CE87C1@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Ok I also tried that Tom. Psql returned “Did not find any relations named “‘.temp_my_table_global”
Sent from my iPad
> On Nov 2, 2020, at 11:31 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> John Scalia <jayknowsunix(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | S Bob | 2020-11-02 16:41:29 | How to analyze a core dump |
Previous Message | Tom Lane | 2020-11-02 16:31:17 | Re: Maybe a possible bug in the partitioning code? |