Re: Segfault related to pg_authid when running initdb from git master - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Segfault related to pg_authid when running initdb from git master
Date
Msg-id AANLkTinbXyMV9A5KfH+PZHUMJSOP2Lf=ZJKg-QHRwFYX@mail.gmail.com
Whole thread Raw
In response to Re: Segfault related to pg_authid when running initdb from git master  (Peter Geoghegan <peter.geoghegan86@gmail.com>)
Responses Re: Segfault related to pg_authid when running initdb from git master  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Dec 15, 2010 at 12:39 PM, Peter Geoghegan
<peter.geoghegan86@gmail.com> wrote:
> Observe that the initdb and postgres timestamps are the same.

Hrm.

>>> I cannot find the coredump. Perhaps it's a permissions issue. What do you think?
>>
>> It would presumably get dumped into the data directory.  So if
>> --noclean isn't used I expect it'll get nuked.
>
> It isn't there...it just looks like a virginal PGDATA directory.

Double hrm.

I have no idea how you can be getting line number information for
initdb but not postgres.  I think what you're getting from postgres is
normally what I'd expect to see without --enable-debug.  It sounds
like you are doing it right, but I have no explanation for the
results.

What distro are you using?  This can't be broken across the board,
given the lack of metoos.  Can you use git bisect to figure out which
commit broke it?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Daniel Popowich
Date:
Subject: range intervals in window function frames
Next
From: Dmitriy Igrishin
Date:
Subject: Re: hstores in pl/python