pg.ddx.io pgsql-performance@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Michael Parker <parkerm@pobox.com>
To: pgsql-performance@postgresql.org
Subject: Re: Performance problems testing with Spamassassin 3.1.0
Date: Mon, 01 Aug 2005 17:09:07 -0500
Message-ID: <42EE9D83.8000405@pobox.com> (raw)
In-Reply-To: <20050801214931.GF60019@decibel.org>
References: <42E9749F.6000709@aptalaska.net>
<1122616211.5691.340.camel@lamb.mcmillan.net.nz>
<42EA6966.8090402@aptalaska.net>
<1122668371.5691.352.camel@lamb.mcmillan.net.nz>
<19405.1122670917@sss.pgh.pa.us>
<42EAA410.9010700@aptalaska.net>
<27897.1122748133@sss.pgh.pa.us>
<42EE8043.1050207@aptalaska.net>
<op.suulgxokth1vuj@localhost>
<42EE93F8.5010003@aptalaska.net>
<20050801214931.GF60019@decibel.org>
Jim C. Nasby wrote:
>I'm not sure who's responsible for DBI::Pg (Josh?), but would it make
>sense to add better support for bytea to DBI::Pg? ISTM there should be a
>better way of doing this than adding gobs of \'s.
>
>
It has support for binding a bytea parameter, but in this case we're
trying to build up an array and pass that into a stored procedure. The
$dbh->quote() method for DBD::Pg lacks the ability to quote bytea
types. There is actually a TODO note in the code about adding support
for quoting Pg specific types. Presumabliy the difficulties we are
having with this would be solved by that, once it has been implemented.
In the meantime, I believe it's just a matter of getting the right
escapes happen so that the procedure is inserting values that we can
later get via a select and using bind_param() with the PG_BYTEA type.
Michael
Attachments:
signature.asc (application/pgp-signature, 185B) download
view thread (62+ messages) latest in thread
Message-ID: <42EE9D83.8000405@pobox.com> Permalink: ../42EE9D83.8000405@pobox.com/ Also on: postgresql.org/message-id/42EE9D83.8000405@pobox.com ·
reply
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Reply to all the recipients using the --to and --cc options: reply via email To: pgsql-performance@postgresql.org Cc: parkerm@pobox.com Subject: Re: Performance problems testing with Spamassassin 3.1.0 In-Reply-To: <42EE9D83.8000405@pobox.com> * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox