From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
Cc: | Pascal Tufenkji <ptufenkji(at)usj(dot)edu(dot)lb>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Temp tables |
Date: | 2013-05-23 20:32:34 |
Message-ID: | 18426.1369341154@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Steve Crawford <scrawford(at)pinpointresearch(dot)com> writes:
> On 05/23/2013 12:24 AM, Pascal Tufenkji wrote:
>> When I type the following, the database gives me an error:
>> dragon=# CREATE TEMP TABLE _parcours (id int);
>> ERROR: type "_parcours" already exists
Perhaps you have a type or temp table named "parcours"? If so,
"_parcours" is the internal name of the associated array type.
You'll need to use a different name.
> It feels a bit like there is something leftover from a previous process
> that was using the same connection.
We have seen a small number of reports where it seemed that some catalog
entry(s) associated with temp tables didn't get dropped when they should
have been. No one's been able to create a reproducible case though.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Melvin Call | 2013-05-23 21:01:56 | New role, no database |
Previous Message | Steve Crawford | 2013-05-23 19:42:15 | Re: Temp tables |