On Wed, Oct 22, 2008 at 8:07 AM, Andrew Chernow <[EMAIL PROTECTED]> wrote: >>> You mean that when results are asked in textual representation (the >>> default), data is sent on network directly as text? >> >> You should know that text/binary conversions rarely play a significant >> role in terms of performance. There are exceptions...large bytea >> columns, or enormous sets of integers. This is coming from a guy that >> co-wrote a library that allows you to pull data directly in binary. >> >> merlin >> > > If I remember correctly, composites and composite arrays also show worth > while performance gains. libpq array and composite handling is what > initially spawned the libpqtypes project (which required providing type > handling for every basic type like int and text). So, different types were > implemented for different reasons, it was not all performance. The ultimate > functionality we were looking for was multiple result sets, which composite > arrays solve nicely.
sure. That isn't, strictly speaking, a performance argument...it's also a convenience thing. You won't see a difference either way unless the arrays are large, or a lot of them (big result sets). For smaller result sets, the overhead of executing the query is where all the time is spent. merlin -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
