Re: 7.3 LOCK TABLE problem

Sorry... wrote the code specifically for the email, and didn't run it through
the perl -c syntax checker. I was merely trying to get the general idea of the
process of the script. Consider "my $procid = $$;" in the code somewhere, and
for argument's sake, all the ;'s and {'s and }'s in the right places.

IMO, this isn't a perl problem unless the problem is an incompatiblity in the
"PgSQL" module with 7.3.1.

If I can reproduce this on a clean install of PostgreSQL, then what next?

CG

--- Neil Conway <neilc(at)samurai(dot)com> wrote:
> On Mon, 2003-01-27 at 15:21, Chris Gamache wrote:
> > BEGIN;
> > LOCK TABLE queue IN EXCLUSIVE MODE;
> > UPDATE queue
> > set status=$$
> > WHERE id = (SELECT min(id)
> > FROM queue
> > WHERE status=0);
>
> This is unrelated, but note that the sub-select would probably be faster
> written as:
>
> SELECT id FROM queue WHERE status = 0 ORDER BY id ASC LIMIT 1;
>
> As this form of the query can use a btree index on "id" if one's
> present.
>
> > SELECT id, data
> > FROM queue
> > WHERE status=$procid;
>
> My Perl's a bit rusty, but AFAICS $procid is undefined. Perhaps 'perl
> -w' and "use strict;" would be a good idea?
>
> Cheers,
>
> Neil
>
> --
> Neil Conway <neilc(at)samurai(dot)com> || PGP Key ID: DB3C29FC
>
>
>

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com