Re: Using Cursor in PostgreSQL 7.2

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Conway <joseph(dot)conway(at)home(dot)com>
Cc: Doug McNaught <doug(at)wireboard(dot)com>, Holger Krug <hkrug(at)rationalizer(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Using Cursor in PostgreSQL 7.2
Date: 2001-12-07 21:38:48
Message-ID: 2638.1007761128@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers pgsql-patches

Joe Conway <joseph(dot)conway(at)home(dot)com> writes:
> It looks like the stats monitoring functions suffer from the same
> limitation that I hit with dblink:

Urgh, you're right:

regression=# select * from pg_stat_activity;
datid | datname | procpid | usesysid | usename | current_query
---------+------------+---------+----------+----------+---------------
3833396 | regression | 2625 | 1 | postgres |
(1 row)

regression=# select * from pg_stat_activity where procpid = 2625;
ERROR: Set-valued function called in context that cannot accept a set
regression=#

This probably qualifies as a "must fix" problem. I guess I'll have to
add the test for set-valued functions that I was reluctant to add
before.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Joe Koenig 2001-12-07 21:54:27 Where do I learn about optimization?
Previous Message Marc Munro 2001-12-07 21:27:42 Virtual Private Database

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephan Szabo 2001-12-07 21:41:46 Re: [SQL] how to change the type
Previous Message Stephan Szabo 2001-12-07 21:34:32 Re: pg_dump: Sorted output, referential integrity

Browse pgsql-patches by date

  From Date Subject
Next Message Serguei Mokhov 2001-12-08 19:09:16 NLS (Russian) - pg_dump update
Previous Message Holger Krug 2001-12-07 19:06:11 Re: Using Cursor in PostgreSQL 7.2