Skip Menu |

This queue is for tickets about the DBD-Pg CPAN distribution.

Report information
The Basics
Id: 33192
Status: resolved
Priority: 0/
Queue: DBD-Pg
People
Owner: Nobody in particular
Requestors: robertlandrum [...] gmail.com
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Tue Feb 12 14:12:40 2008 robertlandrum [...] gmail.com - Ticket created
Subject: Placeholder Bug in DBD::Pg 1.49
Date: Tue, 12 Feb 2008 14:04:38 -0500
To: bug-DBD-Pg [...] rt.cpan.org
From: "Robert Landrum" <robertlandrum [...] gmail.com>
I've attached a script that details the problem with placeholders in DBD::Pg 1.49 as compiled against PostgresQL 8.2.4. Basically SELECT * FROM table WHERE field ~ '^regex'; is fast and SELECT * FROM table WHERE field ~ ?; is very very slow. The server side is 8.2.4 as well. This problem only recently presented itself when we upgraded the client side libs (and recompiled DBD::Pg) from PostgresQL 7.4. Prior to that, placeholders in regex fields worked fine. I have not experienced any issue with other types of placeholders (i.e. WHERE foo = ? or bar in(?)). Rob

Message body is not shown because sender requested not to inline it.

  Tue Feb 12 14:36:21 2008 perl [...] bigrob.ath.cx - Correspondence added
From: perl [...] bigrob.ath.cx
On Tue Feb 12 14:12:40 2008, robertlandrum@gmail.com wrote: Show quoted text
> I've attached a script that details the problem with placeholders in > DBD::Pg 1.49 as compiled against PostgresQL 8.2.4. > > Basically > > SELECT * FROM table WHERE field ~ '^regex'; > > is fast and > > SELECT * FROM table WHERE field ~ ?; > > is very very slow. > > The server side is 8.2.4 as well. This problem only recently > presented itself when we upgraded the client side libs (and recompiled > DBD::Pg) from PostgresQL 7.4. Prior to that, placeholders in regex > fields worked fine. I have not experienced any issue with other types > of placeholders (i.e. WHERE foo = ? or bar in(?)). > > Rob
I've found that problem is mitigated by following the suggestion from Bug #18133.
  Tue Feb 12 14:36:23 2008 The RT System itself - Status changed from 'new' to 'open'
  Thu Feb 21 11:23:02 2008 greg [...] turnstep.com - Status changed from 'open' to 'resolved'