From: Greg Sabino Mullane <greg@turnstep.com>
To: pgsql-performance@postgresql.org
Subject: Re: Perl DBD and an alarming problem
Date: Wed, 16 Nov 2005 23:30:44 -0000
Message-ID: <b61d71c1a4056df4bd92b29656c2f16a@biglumber.com> (raw)
In-Reply-To: <437B9DA9.2030806@modgraph-usa.com>
-----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@turnstep.com
PGP Key: 0x14964AC8 200511161830
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iD8DBQFDe8ErvJuQZxSWSsgRAoZ6AJ9h6gV5U7PyLDJIqXLpSB6r7NWaaQCdESSR
CdNexfvYvSQjOLkEdPXd26U=
=/W5F
-----END PGP SIGNATURE-----
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: greg@turnstep.com
Subject: Re: Perl DBD and an alarming problem
In-Reply-To: <b61d71c1a4056df4bd92b29656c2f16a@biglumber.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