On Fri, Nov 16, 2012 at 11:09 AM, Sébastien Lardière
wrote:
> On 11/15/2012 08:40 PM, Cédric Villemain wrote:
>> top post: this looks like a plproxy bug (no ?), I've added Marko in CC.
>
> Yes, it is, i think …
Thanks, fixed in git. Fix will be in 2.5 release.
--
marko
--
Sent via pgsql-gen
On 11/15/2012 08:40 PM, Cédric Villemain wrote:
> top post: this looks like a plproxy bug (no ?), I've added Marko in CC.
Yes, it is, i think …
>
>
>> I've a segfault on a PostgreSQL 9.1 cluster, with a plproxy function
>> call. Both PostgreSQL and plproxy are up to date. I use SQL/MED in that
>
top post: this looks like a plproxy bug (no ?), I've added Marko in CC.
> I've a segfault on a PostgreSQL 9.1 cluster, with a plproxy function
> call. Both PostgreSQL and plproxy are up to date. I use SQL/MED in that
> specific case, but it's the same without. I reproduced the following
> scenario
Hi,
I've a segfault on a PostgreSQL 9.1 cluster, with a plproxy function
call. Both PostgreSQL and plproxy are up to date. I use SQL/MED in that
specific case, but it's the same without. I reproduced the following
scenario on a few clusters, with or without streaming replication.
On a given clust
