Re: pgsql: Use slots in trigger infrastructure, except for theactual invoc - Mailing list pgsql-committers

From Andres Freund
Subject Re: pgsql: Use slots in trigger infrastructure, except for theactual invoc
Date
Msg-id 20190227181621.xholonj7ff7ohxsg@alap3.anarazel.de
Whole thread Raw
In response to Re: pgsql: Use slots in trigger infrastructure, except for the actualinvoc  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Responses Re: pgsql: Use slots in trigger infrastructure, except for theactual invoc  (Andres Freund <andres@anarazel.de>)
List pgsql-committers
On 2019-02-27 12:59:16 -0500, Andrew Dunstan wrote:
> 
> On 2/27/19 1:22 AM, Andres Freund wrote:
> > Hi,
> >
> > On 2019-02-27 04:41:28 +0000, Andres Freund wrote:
> >> Use slots in trigger infrastructure, except for the actual invocation.
> > Andrew, I see that this broke crake's redis_fdw check. I see it actually
> > fails with an error, rather than fail to build. Could you perhaps enable
> > generating backtraces?
> 
> 
> Not sure why it should fail to build.

Oh, because one of the options was that it used a slot from a variable
name that doesn't exist anymore...


> Backtraces should be enabled in the animal - I will investigate why
> we're not getting them here. Meanwhile, here's one for this problem:

Thanks, that helps!  My first theories as to what's going on fell flat,
unfortunately. I guess I'll have to figure out how to run that locally
:(.

Greetings,

Andres Freund


pgsql-committers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: pgsql: Use slots in trigger infrastructure, except for the actualinvoc
Next
From: Peter Eisentraut
Date:
Subject: pgsql: Remove unused macro