From: | Daniel Ceregatti <daniel(at)omnis(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | josh(at)agliodbs(dot)com, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Error in 8.0 rc5 with repeat calls to array operator |
Date: | 2005-01-17 03:08:22 |
Message-ID: | 41EB2C26.7000206@omnis.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
This doesn't happen on a fresh initdb. In fact, it doesn't happen even
directly after I load data. It might take a day or two, but eventually
the problem manifests itself. I can reproduce it 100% of the time now.
I've noticed this on 8rc1-5. Josh and I will get you a gdb trace ASAP.
Daniel
Tom Lane wrote:
>Josh Berkus <josh(at)agliodbs(dot)com> writes:
>
>
>>However, we're found that if you run thousands of empty array comparisons in a
>>few seconds/minutes, eventually the empty array comparison breaks, and you
>>get:
>>ERROR: cache lookup failed for function 0
>>
>>
>
>I tried
>
>while true; do echo "select '{}'::INT[] = '{}'::INT[];" ; done | psql regression >/dev/null
>
>on a couple different platforms, with and without INTARRAY (which
>isn't invoked by this query anyway, so I doubt it matters). I haven't
>seen any misbehavior yet.
>
>If you can reproduce this, please attach to the backend with gdb, set a
>breakpoint at errfinish(), and get a stack traceback from the point of
>the error.
>
> regards, tom lane
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | manikanti sreedhar reddy | 2005-01-17 09:27:27 | BUG #1406: subsequent WHEN/ELSE is getting validated, eventhough prior WHEN condition is true |
Previous Message | Michael Fuhr | 2005-01-17 02:56:49 | Re: BUG #1393: Adding 'LIMIT 1' to the query halts forever |