Alvaro Herrera wrote: > Tom Lane wrote: > > Alvaro Herrera <[EMAIL PROTECTED]> 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 ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
