Re: Failure on markhor with CLOBBER_CACHE_ALWAYS for test brin - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Failure on markhor with CLOBBER_CACHE_ALWAYS for test brin
Date
Msg-id 20141231143726.GD19836@alap3.anarazel.de
Whole thread Raw
In response to Re: Failure on markhor with CLOBBER_CACHE_ALWAYS for test brin  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Failure on markhor with CLOBBER_CACHE_ALWAYS for test brin
List pgsql-hackers
On 2014-12-31 10:02:40 -0300, Alvaro Herrera wrote:
> Alvaro Herrera wrote:
> > Michael Paquier wrote:
> > > HI all.
> > > 
> > > markhor has run for the first time in 8 days, and there is something
> > > in range e703261..72dd233 making the regression test of brin crashing.
> > > See here:
> > > http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=markhor&dt=2014-12-30%2020%3A58%3A49
> > 
> > This shows that the crash was in the object_address test, not brin.
> > Will research.
> 
> I can reproduce the crash in a CLOBBER_CACHE_ALWAYS build in
> the object_address test.  The backtrace is pretty strange:

Hard to say without more detail, but my guess is that the argument to
get_collation_oid() isn't actually valid. For one, that'd explain the
error, for another, the pointer's value (name=name@entry=0x11655c0) is
suspiciously low.

> #8  0x0000000000504699 in get_collation_oid (name=name@entry=0x11655c0, 
>     missing_ok=missing_ok@entry=0 '\000')
>     at /pgsql/source/master/src/backend/catalog/namespace.c:3323
> #9  0x000000000050d8dc in get_object_address (objtype=objtype@entry=OBJECT_COLLATION, 
>     objname=objname@entry=0x11655c0, objargs=objargs@entry=0x0, 
>     relp=relp@entry=0x7fff24432c28, lockmode=lockmode@entry=1, 
>     missing_ok=missing_ok@entry=0 '\000')
>     at /pgsql/source/master/src/backend/catalog/objectaddress.c:704

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Additional role attributes && superuser review
Next
From: Magnus Hagander
Date:
Subject: Re: Additional role attributes && superuser review