Hi,
After stopping the eecution of some external program which use postgre, one
temporary table wasnt automatically erased.
It still exists in pg_temp_14 schema.
May i drop that table and that schema manually? (will it cause some
problems)?
Thanx in advance
--
---
David W Noon writes:
> On Sat, 06 Nov 2010 11:59:48 -0400, Tom Lane wrote about Re: [ADMIN]
>> In general, NOT IN is hard to optimize because of its weird behavior
>> for NULLs. I'd suggest looking into converting the query to use an
>> EXISTS instead.
> I have know about that issue for some yea
On Sat, 06 Nov 2010 11:59:48 -0400, Tom Lane wrote about Re: [ADMIN]
Interesting Query Performance Question:
>In general, NOT IN is hard to optimize because of its weird behavior
>for NULLs. I'd suggest looking into converting the query to use an
>EXISTS instead.
I have know about that issue for
"Jonathan Hoover" writes:
> [ poor performance with NOT IN ]
> Query E then is apparently the way to go, but shouldn't there be a way
> to get the query planner to take these steps itself? If A had ever
> finished, I'd sure like to have seen an EXPLAIN ANALYZE on it.
Well, just an EXPLAIN would
Any explanation for this is appreciated...
I had a query which just seemed to peg the processor. I decided to let it go
all night, and after 16 hours, it was still stuck at 100% processor usage. I
figured something must be wrong, so I tried a few things. Using the following
logic, I was able to
