Re: Bugfix and new feature for PGXS

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Bruce Momjian <bruce(at)momjian(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: cedric(at)2ndquadrant(dot)com, pgsql-hackers(at)postgresql(dot)org, Josh Berkus <josh(at)agliodbs(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>
Subject: Re: Bugfix and new feature for PGXS
Date: 2014-12-04 19:44:59
Message-ID: 5480B9BB.6060301@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/4/14 11:38 AM, Peter Eisentraut wrote:
> On 11/19/14 11:11 PM, Peter Eisentraut wrote:
>> I noticed this item was still in the 9.4 code. Looking at the original
>> submission
>> (http://www.postgresql.org/message-id/201306181552.36673.cedric@2ndquadrant.com,
>> patch 0001), I think the original reason for adding this was wrong to
>> begin with.
>
> I have applied all three patches to 9.4 and 9.5. So this issue is now
> resolved.

Apparently, some buildfarm module is unhappy with this:

http://buildfarm.postgresql.org/cgi-bin/show_stage_log.pl?nm=sittella&dt=2014-12-04%2017%3A16%3A29&stg=RedisFDW-build

Is there some custom code running there? I don't know how that error
would happen otherwise?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Matt Newell 2014-12-04 19:45:28 Re: libpq pipelining
Previous Message Claudio Freire 2014-12-04 19:30:27 Re: libpq pipelining