Re: BUG #5883: Error when mixing SPI_returntuple with returning regular HeapTuple

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Vegard Bønes <vegard(dot)bones(at)met(dot)no>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5883: Error when mixing SPI_returntuple with returning regular HeapTuple
Date: 2011-02-17 01:41:47
Message-ID: AANLkTinQ5wDjw_LV4y1phOjHhWotRjQUuDtVry9CzWKC@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Feb 15, 2011 at 2:43 AM, Vegard Bønes <vegard(dot)bones(at)met(dot)no> wrote:
> Ok, I tried to modify the example functions get_data_alternative_a() and get_data_alternative_b(), so that they start with SPI_connect, and end with SPI_finish. Also I removed SPI_connect and SPI_finish from the main function. As I understand you, that should have solved the problem. The result, however, is exactly the same as before.

You may get further if you post the modified code, instead of simply
asserting that some code we can't see doesn't work.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2011-02-17 04:38:01 Re: Bidirectional replication for postgres 9
Previous Message Tom Lane 2011-02-16 22:46:52 Re: BUG #5890: malloc error