By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,933 Members | 1,676 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,933 IT Pros & Developers. It's quick & easy.

why I can call pg_stat_get_backend_idset directly

P: n/a
Hello

Iam play with SRF function and found difference between behavior system
function pg_stat_get_backend_idset and own function in plpgsql;

aopk=> \df pg_stat_get_backend_idset
Datový typ výsledku | Schéma | Jméno | Datový typ
parametru
---------------------+------------+---------------------------+----------------------
setof integer | pg_catalog | pg_stat_get_backend_idset |
aopk=> \df aa
Datový typ výsledku | Schéma | Jméno | Datový typ parametru
---------------------+--------+-------+----------------------
setof integer | public | aa |
(1 řádka)

I can select * from pg_stat_get_backend_idset();
I can select * from aa()

I understand, but I can call too

select pg_stat_get_backend_idset();
pg_stat_get_backend_idset
---------------------------
1
2
(2 řádek)

This isn't right for srf function, or else. I wont write own srf function
with equal feature - similir like MSSQL procedures. It's possible?

Regards

Pavel


---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

Nov 12 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.