BUG #13516: no binary output function available for type void

Started by Nuri Boardmanover 10 years ago3 messagesbugs
Jump to latest
#1Nuri Boardman
ganuri@gmail.com

The following bug has been logged on the website:

Bug reference: 13516
Logged by: Nuri Boardman
Email address: ganuri@gmail.com
PostgreSQL version: 9.0.4
Operating system: Windows 7
Description:

calling a stored procedure which has return type void

using PQexecParams
and passing 1 for the last argument (binary results)

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Nuri Boardman (#1)
Re: BUG #13516: no binary output function available for type void

ganuri@gmail.com writes:

The following bug has been logged on the website:
Bug reference: 13516
Logged by: Nuri Boardman
Email address: ganuri@gmail.com
PostgreSQL version: 9.0.4
Operating system: Windows 7
Description:

calling a stored procedure which has return type void
using PQexecParams
and passing 1 for the last argument (binary results)

That was fixed way back in 9.1.

Since 9.0.x will be out of support this fall, you really should be
thinking about an upgrade.

regards, tom lane

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

#3Nuri Boardman
ganuri@gmail.com
In reply to: Tom Lane (#2)
Re: BUG #13516: no binary output function available for type void

We're going to 9.4 very shortly. Thanks for letting me know it's fixed.
On Jul 23, 2015 6:58 PM, "Tom Lane" <tgl@sss.pgh.pa.us> wrote:

Show quoted text

ganuri@gmail.com writes:

The following bug has been logged on the website:
Bug reference: 13516
Logged by: Nuri Boardman
Email address: ganuri@gmail.com
PostgreSQL version: 9.0.4
Operating system: Windows 7
Description:

calling a stored procedure which has return type void
using PQexecParams
and passing 1 for the last argument (binary results)

That was fixed way back in 9.1.

Since 9.0.x will be out of support this fall, you really should be
thinking about an upgrade.

regards, tom lane