Re: strange buildfarm failures - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: strange buildfarm failures
Date
Msg-id 20070502142626.GL4585@alvh.no-ip.org
Whole thread Raw
In response to Re: strange buildfarm failures  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: strange buildfarm failures
List pgsql-hackers
Alvaro Herrera wrote:
> Tom Lane wrote:
> > Alvaro Herrera <alvherre@commandprompt.com> writes:
> > > I agree that that would be a bug and we should fix it, but I don't think
> > > it explains the problem we're seeing because there is no PG_TRY block
> > > in the autovac startup code that I can see :-(
> > 
> > I'm wondering if there is some code path that invokes a PG_TRY deep in
> > the bowels of the system.
> 
> Well, I checked all the bowels involved in autovacuum startup.

Huh, hang on ... there is one caller, which is to set client_encoding
(call_string_assign_hook uses a PG_TRY block), but it is called *after*
the sigsetjmp block -- in InitPostgres.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Teodor Sigaev
Date:
Subject: Re: Patch queue triage
Next
From: Tom Lane
Date:
Subject: Re: strange buildfarm failures