Skip site navigation (1) Skip section navigation (2)

plperl vs. bytea

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Theo Schlossnagle <jesus(at)omniti(dot)com>
Subject: plperl vs. bytea
Date: 2007-05-06 01:46:11
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
I have been talking with Theo some more about his recent problem with 
bytea arguments and results (see recent discussion on -bugs and also 
recent docs patch),  what he needs is a way to have bytea  (and possibly 
other unknown types) passed as binary data to and from plperl. The 
conversion overhead is too big both computationally and  in increased 
memory usage. After discussing some possibilities, we decided that maybe 
the best approach would be to allow a custom GUC variable that would 
specify a list of types to be passed in binary form with no conversion, e.g.

  plperl.pass_as_binary = 'bytea, other-type'

This would affect function args, trigger data, return results, and I 
think it should also apply to arguments for SPI prepared queries and to 
SPI returned results.

If this seems like a good idea maybe it should go on the TODO list in 
whatever is the current incarnation.




pgsql-hackers by date

Next:From: Andrew DunstanDate: 2007-05-06 01:49:54
Subject: Re: Integer datetimes
Previous:From: Bruce MomjianDate: 2007-05-06 01:28:30
Subject: Re: Integer datetimes

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group