pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: John Scalia <jayknowsunix@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
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> (raw)
In-Reply-To: <656221.1604334677@sss.pgh.pa.us>
References: <656221.1604334677@sss.pgh.pa.us>

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@sss.pgh.pa.us> wrote:
> 
> 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





view thread (5+ messages)  latest in thread

Message-ID: <5F7F8C76-DA88-46D6-B0B6-DB9C84CE87C1@gmail.com>
Permalink:  ../5F7F8C76-DA88-46D6-B0B6-DB9C84CE87C1@gmail.com/
Also on:    postgresql.org/message-id/5F7F8C76-DA88-46D6-B0B6-DB9C84CE87C1@gmail.com

 · 

reply

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: jayknowsunix@gmail.com, tgl@sss.pgh.pa.us
  Subject: Re: Maybe a possible bug in the partitioning code?
  In-Reply-To: <5F7F8C76-DA88-46D6-B0B6-DB9C84CE87C1@gmail.com>

* 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