Re: Batch processing - Mailing list pgsql-general

From Franco Bruno Borghesi
Subject Re: Batch processing
Date
Msg-id 1059487839.2945.30.camel@taz.oficina
Whole thread Raw
In response to Batch processing  (gnotari@linkgroup.it)
List pgsql-general
Maybe the best option (specialy if you need users to control the jobs) would be to create a table like this:

CREATE TABLE batchjobs (
   id SERIAL,
   sql TEXT NOT NULL,
   done BOOLEAN NOT NOOL DEFAULT false
);

Then you create a pl/pgsql function that iterates every "undone" record from this table
and EXECUTEs the query from the sql field (and sets the done field to true).

You can run this process from crontab let's say, every 15 minutes  (only if this process is not already running) with a
echo "SELECT * FROM runJobs();"| psql ...

Hope this helps.


On Tue, 2003-07-29 at 05:28, gnotari@linkgroup.it wrote:
I'm in the need of something similar to Oracle's batch processing, in
Postgres.
I would like to have something like a queue of "requests" (SQL selects),
run one by one, so not to overload the server -- every SELECT is
'intensive'.

How would you implement such a thing?

ciao
Guido



---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
Attachment

pgsql-general by date:

Previous
From: "Dave [Hawk-Systems]"
Date:
Subject: determine how many matches of a string in a field
Next
From: Ron Johnson
Date:
Subject: Re: concurrent writes