<div>
<div class="content wysiwyg-content">
Hello fellow postgresql experts,<br />
<br />
I was wandering about the opportunity to use table-valued functions vs functions returning output sets. &nbsp;From your experience, which one, &nbsp;assuming all indexes are in place, presents the best performance regarding :<br />
<br />
&gt;&nbsp;Concurrent accesses. &nbsp;<br />
&gt;&nbsp;Handling by the optimizer<br />
&gt;&nbsp;CPU and IO execution usage.<br />
&gt;&nbsp;Locking<br />
<br />
I would appreciate you enlighten me on the above. &nbsp;Thank you for your help.
</div>
</div>


Hello fellow postgresql experts,

I was wandering about the opportunity to use table-valued functions vs functions returning output sets.  From your experience, which one,  assuming all indexes are in place, presents the best performance regarding :

> Concurrent accesses.  
> Handling by the optimizer
> CPU and IO execution usage.
> Locking

I would appreciate you enlighten me on the above.  Thank you for your help.

Table valued vs OUT function's performance in postgresql

PostgreSQL is an object-relational database management system with an emphasis on extensibility and standards-compliance. As a database server, its primary function is to store data securely, supporting best practices, and to allow for retrieval at the request of other software applications. PostgreSQL implements the majority of the SQL2011 standard, is ACID-compliant and transactional using multiversion concurrency control (MVCC), and handles complex SQL queries using many indexing methods that are not available in other databases. It is cross-platform and runs on many operating systems including Linux, FreeBSD, OS X, Solaris, and Microsoft Windows.