Message-ID: <437B9DA9.2030806@modgraph-usa.com>
Date: Wed, 16 Nov 2005 12:59:21 -0800
From: "Craig A. James" <cjames@modgraph-usa.com>
User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716)
MIME-Version: 1.0
Cc: Pgsql-Performance <pgsql-performance@postgresql.org>
Subject: Perl DBD and an alarming problem
References: <BF9F6C0E.13B4A%llonergan@greenplum.com>
	<1132136225.5711.4.camel@Panoramix>
In-Reply-To: <1132136225.5711.4.camel@Panoramix>
Content-Type: text/plain; charset=ISO-8859-13; format=flowed
Content-Transfer-Encoding: 7bit

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

   eval {
      local $SIG{ALRM} = sub {die("Timeout");};
      $time = gettimeofday;
      alarm 20;
      $sth = $dbh->prepare("a query that may take a long time...");
      $sth->execute();
      alarm 0;
   };
   if ($@ && $@ =~ /Timeout/) {
      my $elapsed = gettimeofday - $time;
      print "Timed out after $elapsed seconds";
   }

Now the mystery: It works, but it hardly matters what time I use for the alarm call, the actual alarm event always happens at 26 seconds.  I can set "alarm 1" or "alarm 20", and it almost always hits right at 26 seconds.

Now if I increase alarm to anything in the range of about 25-60 seconds, the actual alarm arrives somewhere around the 90 second mark.  It seems as though there are "windows of opportunity" for the alarm, and it is ignored until those "windows" arrive.

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

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

Thanks,
Craig