Re: Sleep functions - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Sleep functions
Date
Msg-id 16361.1124726002@sss.pgh.pa.us
Whole thread Raw
In response to Re: Sleep functions  (Robert Treat <xzilla@users.sourceforge.net>)
Responses Re: Sleep functions  (Robert Treat <xzilla@users.sourceforge.net>)
Re: Sleep functions  ("Jim C. Nasby" <jnasby@pervasive.com>)
List pgsql-hackers
Robert Treat <xzilla@users.sourceforge.net> writes:
>> On Aug 22, 2005, at 12:40 AM, Michael Fuhr wrote:
>>> To others who've written their own sleep() function: what are you
>>> using it for?

> I know I've used one for a script that reindexes various tables on an
> old 7.3 server. I put a sleep of 20 seconds between reindexes to let
> built up transactions have a few moments to catch up, thereby smoothing
> out i/o. For a long time I used a cpu hogging plpgsql version (since I
> had cpu to spare) until I switched to a better pltcl version. If a
> server side one existed I would certainly have used that. 

Tell you the truth, this "use case" qualifies as a poster child for my
concern that a server-side sleep would encourage people to write code
that sits on locks.  If you'd coded some kind of plpgsql loop that did
a REINDEX, sleep N seconds, another REINDEX, etc, you'd have been
sitting on the exclusive lock for each table until the end of the whole
transaction.  Your approach makes lots of sense if you commit each
REINDEX transaction and sleep *outside* the transaction --- but a server
sleep function would do exactly not that.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: Missing CONCURRENT VACUUM (Was: Release notes for
Next
From: Tom Lane
Date:
Subject: Re: enable_constraint_exclusion GUC name