From: | Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | why I can call pg_stat_get_backend_idset directly |
Date: | 2004-01-08 17:37:28 |
Message-ID: | Pine.LNX.4.44.0401081830030.32257-100000@kix.fsv.cvut.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Lebedev | 2004-01-08 18:20:27 | deferring/disabling unique index |
Previous Message | Ben | 2004-01-08 17:30:05 | Re: Simulation output using libpq |