On 10/11/2013 08:36 AM, Alvaro Herrera wrote:
Adrian Klaver escribió:
On 10/11/2013 03:51 AM, hiroyuki shiga wrote:
Thank you for reply.
but .... I can't provide a self-contained test case.
So what are you doing when you get the core dump?
The query is in the backtrace:
SELECT PATH, COUNT(SITE_ID)
FROM ACCESS_LOG_05
WHERE SITE_ID = $1
GROUP BY PATH
ORDER BY PATH
And it also suggests that the crash is happening during cache lookup of
the "count" function.
Since this seems to work for pretty much everybody, I would wonder about
corrupt catalogs and/or corrupt cache; if neither, perhaps some race
condition on cache invalidation/reload. Speculating much without any
further evidence or test case appears pointless.
Which is where I was going with my question. The query would seem to be
the trigger for the core dump, but it does not enlighten as to the lead
up conditions. Basically with out more context answering the question
would involve a lucky guess.
--
Adrian Klaver
adrian.klaver@xxxxxxxxx
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
