On 5/14/23 13:04, FOUTE K. Jaurès wrote:
>
>
> Le dim. 14 mai 2023 à 16:12, Adrian Klaver <adrian.klaver@aklaver.com
> <mailto:adrian.klaver@aklaver.com>> a écrit :
>
> Not what was requested.
>
> In the post linked to here:
>
> https://www.postgresql.org/message-id/CAHQ1jffWF7Y8c1X7EK3JvbLJgw1GEcVk0uPa3%2B0CJo4h8PFHVw%40mail.gmail.com
<https://www.postgresql.org/message-id/CAHQ1jffWF7Y8c1X7EK3JvbLJgw1GEcVk0uPa3%2B0CJo4h8PFHVw%40mail.gmail.com>
>
> there was an image of the result of:
>
> SELECT cron.schedule( 'TEST','30 seconds', $$SELECT 1$$);
>
> Provide that result as text.
>
> jobid | schedule | command | nodename | nodeport |
> database | username | active | jobname
>
-------+------------+----------+-----------+----------+--------------------------------------------+----------+--------+---------
> 8 | 30 seconds | SELECT 1 | localhost | 5692 | databasename |
> postgres | t | TEST
> (1 row)
That is not the same result as in the image, it had additional fields:
runid, job_pid, status, return_message, start_time.
Also the database field had not been edited. In the original image it
looks like there was multiple databases named. From what I understand of
pg_cron a job can only run on one database at a time.
--
Adrian Klaver
adrian.klaver@aklaver.com