Le lun. 15 mai 2023 à 05:12, FOUTE K. Jaurès <jauresfo...@gmail.com> a écrit :
> > > Le dim. 14 mai 2023 à 21:12, Adrian Klaver <adrian.kla...@aklaver.com> a > écrit : > >> On 5/14/23 13:04, FOUTE K. Jaurès wrote: >> > >> > >> > Le dim. 14 mai 2023 à 16:12, Adrian Klaver <adrian.kla...@aklaver.com >> > <mailto:adrian.kla...@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. >> > Okay, Understands now, this result come from cron.job_run_details that > show the status of running job > Select * from cron.job_run_details where jobid =8 order by runid desc > limit 5 > jobid | runid | job_pid | database | > username | command | status | return_message | start_time | end_time > > -------+-------+---------+--------------------------------------------+----------+----------+--------+-------------------+------------+---------- > 8 | 9276 | | inov_victoria_v71_rdec21_00_ibackuppro_rep | > postgres | SELECT 1 | failed | connection failed | | > 8 | 9275 | | inov_victoria_v71_rdec21_00_ibackuppro_rep | > postgres | SELECT 1 | failed | connection failed | | > 8 | 9274 | | inov_victoria_v71_rdec21_00_ibackuppro_rep | > postgres | SELECT 1 | failed | connection failed | | > 8 | 9272 | | inov_victoria_v71_rdec21_00_ibackuppro_rep | > postgres | SELECT 1 | failed | connection failed | | > 8 | 9271 | | inov_victoria_v71_rdec21_00_ibackuppro_rep | > postgres | SELECT 1 | failed | connection failed | | > (5 rows) > >> >> 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. >> > No, it's just one database. > >> >> -- >> Adrian Klaver >> adrian.kla...@aklaver.com >> >> > > -- > Jaurès FOUTE > Hello @Adrian Klaver <adrian.kla...@aklaver.com> . I've just finished a test on PostgreSQL 14 and everything works as expected. -- Jaurès FOUTE
