From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Christopher Browne <cbbrowne(at)acm(dot)org> |
Cc: | slony <slony1-general(at)lists(dot)slony(dot)info>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: logtrigger issue in PostgreSQL HEAD |
Date: | 2010-02-12 19:31:48 |
Message-ID: | 20100212193147.GG3737@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2010-02-12 19:33:12 | Re: Re: [COMMITTERS] pgsql: Reduce the chatter to the log when starting a standby server. |
Previous Message | Boszormenyi Zoltan | 2010-02-12 18:55:36 | Re: [PATCH] Provide rowcount for utility SELECTs |