Re: What is the best way to do this in Postgres - Mailing list pgsql-sql

From Erik Brandsberg
Subject Re: What is the best way to do this in Postgres
Date
Msg-id CAFcck8EkY5D+Q=qOTio4hBVB_yo8rH768eYazRuAKa8OGKkOEA@mail.gmail.com
Whole thread Raw
In response to What is the best way to do this in Postgres  (kunwar singh <krishsingh.111@gmail.com>)
List pgsql-sql
Check the extension ph_cron, while I have never used it, it may be good to use as part of the solution.

On Sun, Dec 8, 2024, 6:39 AM kunwar singh <krishsingh.111@gmail.com> wrote:
Hello Listers,
Looking for your inputs on the most efficient way to do it in Postgres. 

What I want to do:
===
I want to spawn 10 concurrent sessions each executing a complex stored procedure with one of the parameters being the product ID.
Example

CALL process_product(curdate, region, productid=>1) ;
CALL process_product(curdate, region, productid=>2) ;
CALL process_product(curdate, region, productid=>3) ;
CALL process_product(curdate, region, productid=>4) ;
...
CALL process_product(curdate, region, productid=>10) ;


Say I get a list of product IDs by running a big query

Product ID
====
1
2
3
4
..
10


Additional Information
===
Everytime number of product ids will change. At a given time there should be no more than 10 concurrent sessions of process_product.
I want to trigger these procedure calls once every hour. For a given hour the number of product IDs could range from 10 to 100 in total.
I am using RDS Postgres v 15.

Question
===
I know I can create a bash script or Python script , but I am wondering if there is a smarter way to do it in Postgres?



--
Cheers,
Kunwar

pgsql-sql by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: What is the best way to do this in Postgres
Next
From: sulfinu@gmail.com
Date:
Subject: Abitity to identify the current iteration in a recursive SELECT (feature request)