Re: logtrigger issue in PostgreSQL HEAD - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: logtrigger issue in PostgreSQL HEAD
Date
Msg-id 20100212193147.GG3737@alvh.no-ip.org
Whole thread Raw
In response to logtrigger issue in PostgreSQL HEAD  (Christopher Browne <cbbrowne@acm.org>)
List pgsql-hackers
Christopher Browne wrote:

> There are no notable compiler complaints about
> src/backend/slony_funcs.c, so the mismatch must be at a subtler level
> than that of an up-front API change for something.
> 
> I suppose a next step might be to kick off gdb against the backend when
> processing this.

Yeah, let's see a backtrace.  Maybe we need to break an API somewhere so
that this becomes more obvious at compile time.

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


pgsql-hackers by date:

Previous
From: Boszormenyi Zoltan
Date:
Subject: Re: [PATCH] Provide rowcount for utility SELECTs
Next
From: Richard Huxton
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Reduce the chatter to the log when starting a standby server.