pg_timetable VS pg_background

That's easily done with a cron job or something similar (e.g. pg_timetable)

When you are working on Oracle to PostgreSQL migrations, one of the Oracle packages that cause conversion issues is DBMS_JOB. Traditionally, we used extensions like : pg_agent, pg_cron or more recently pg_timetable for scheduling jobs. All of these tools or extensions use a cronjob like scheduling method which does not give a full compatibility of the features provided by Oracle DBMS_JOB. Translating calls to DBMS_JOB.SUBMIT() into a cron setting is more painful than being impossible when there is an execution interval lesser than a minute. There are several such DBMS_JOB compatibility issues including asynchronous scheduling which is not possible with the already existing extensions in PostgreSQL. MigOps hates to stay without Open Source solutions. So, we are announcing PG_DBMS_JOB extension for Oracle DBMS_JOB compatibility, released under PostgreSQL License. An interesting point here is that we have included full compatibility of Oracle DBMS_JOB in PG_DBMS_JOB PostgreSQL extension.

If you don't want to (or can't) use the Windows Scheduler, you might want to try out pg_timetable instead, which also offers Windows binaries.

Try pg_timetable

You better send emails periodically with cron-like scheduler. This one can do both cron and periodical jobs: https://github.com/cybertec-postgresql/pg_timetable

There is an extension which seems to be able to do that though.