Re: Perl DBD and an alarming problem

From: "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Perl DBD and an alarming problem
Date: 2005-11-16 23:30:44
Message-ID: b61d71c1a4056df4bd92b29656c2f16a@biglumber.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> I am mystified by the behavior of "alarm" in conjunction with
> Postgres/perl/DBD. Here is roughly what I'm doing:

> Anyone have a clue what's going on and/or how I can fix it?

Not really, but alarm has never worked well (or claimed to) with
DBI. The DBI docs recommend trying out Sys::Sigaction:

http://search.cpan.org/~lbaxter/Sys-SigAction/

> A secondary question: It appears that $sth->cancel() is not
> implemented in the Pg DBD module. Is that true?

Correct. DBD::Pg does not support asynchronous connections. It's
possible it may in the future, but there has not been much of a
perceived need. Feel free to enter a request on CPAN:

http://rt.cpan.org/NoAuth/Bugs.html?Dist=DBD-Pg

There may be another way around it, if you can tell us some more
about what exactly it is you are trying to do.

- --
Greg Sabino Mullane greg(at)turnstep(dot)com
PGP Key: 0x14964AC8 200511161830
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iD8DBQFDe8ErvJuQZxSWSsgRAoZ6AJ9h6gV5U7PyLDJIqXLpSB6r7NWaaQCdESSR
CdNexfvYvSQjOLkEdPXd26U=
=/W5F
-----END PGP SIGNATURE-----

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Michael Fuhr 2005-11-17 00:23:45 Re: Perl DBD and an alarming problem
Previous Message Cristian Prieto 2005-11-16 22:56:42 PgPool and Postgresql sessions...