Re: [HACKERS] SIGSEGV in 'select * from pg_user' - Mailing list pgsql-hackers

From Thomas G. Lockhart
Subject Re: [HACKERS] SIGSEGV in 'select * from pg_user'
Date
Msg-id 35F3F4D5.358401DB@alumni.caltech.edu
Whole thread Raw
In response to Re: [HACKERS] SIGSEGV in 'select * from pg_user'  (Tatsuo Ishii <t-ishii@sra.co.jp>)
List pgsql-hackers
> I saw this too on my LinuxPPC box. In my case, just doing:
>         select * from pg_user
>
> crashes the backend. The backtrace shows it crashed in chunk_free()
> while committing the transaction. I guess something messed up the
> tables managed by malloc().
>
> Talking about the regression, two tests (constraints, select_views)
> produced core dump. Seems no difference even after applying Bruce's
> latest patches.

I see the same behavior, with a simple "select * from pg_user" enough to
crash the backend, and with the same two regression tests resulting in
core dumps. As I've mentioned earlier, I believe that the select_views
test has been failing for quite a while, where the other problems are
more recent. Presumably the pg_user problem is similar to the
select_views problem??

Would it help to choose a (simple) test case which shows a problem
(either a core dump or the "relation not found" problem) and start
working it through together? We could then exchange notes on what we are
finding.

I'm not absolutely certain that the problems are directly related to
changes for indexing; other changes (the oid removal, the "name" type
changes, others??) happened in the same time frame...

                     - Tom

pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: [HACKERS] SIGSEGV in 'select * from pg_user'
Next
From: Sferacarta Software
Date:
Subject: Re: DELETE FROM TABLE doesn't work (AGAIN)