EPAS v16 release branch

advocacy_docs/pg_extensions/edb_job_scheduler/configuring.mdx

@@ -0,0 +1,38 @@
+---
+title: "Configuring EDB Job Scheduler"
+---
+
+The EDB Job Scheduler has a scheduler process that starts when the database cluster starts. To start the scheduler process, load the EDB Job Scheduler extension using the `shared_preload_libraries` parameter. 
+
+After you load the extension, create the extension using the `CREATE EXTENSION` command. The database in which you're creating the extension must be listed in the `edb_job_scheduler.database_list` parameter.
+
+The `CREATE EXTENSION` command also creates two tables in the `sys` schema: `jobs` and `job_run_details`. 
+
+In addition, the EDB Job Scheduler provides two more GUCs:
+
+- `edb_job_scheduler.max_jobs_per_database` — Controls the maximum number of jobs per database level. 
+- `edb_job_scheduler.max_workers_per_database` — Controls the maximum number of worker processes per database level.
+
+To apply your changes, reload the configuration using `pg_reload_conf()` or `pg_ctl reload`. 
+
+## Example
+
+This example configures the EDB Job Scheduler extension.
+
+1. Set the GUC parameter and the shared libraries parameter in `postgresql.conf`:
+
+   ```ini
+   edb_job_scheduler.database_list = 'edb'
+   shared_preload_libraries='$libdir/edb_job_scheduler' 
+   ```
+
+2. Restart the database server.
+
+3. Create the extension:
+
+   ```sql
+   # Using psql, connect to edb database as superuser
+   psql -d edb -U enterprisedb
+   # Create the extension
+   CREATE EXTENSION edb_job_scheduler;
+   ```

advocacy_docs/pg_extensions/edb_job_scheduler/index.mdx

@@ -0,0 +1,50 @@
+---
+title: 'EDB Job Scheduler'
+directoryDefaults:
+   product: EDB Job Scheduler
+---
+
+EDB Job Scheduler is an extension that runs the job scheduler as a background process for the `DBMS_SCHEDULER` and `DBMS_JOB` packages.
+
+By default, the `edb_job_scheduler` extension resides in the `contrib/dbms_scheduler_ext` subdirectory under the EDB Postgres Advanced Server installation.
+
+The extension has a main background process called the *launcher*. The launcher process starts when the database cluster loads. It forks the scheduler processes, creating one for each configured database. The databases are configured by the GUC `edb_job_scheduler.database_list`. 
+
+If a database doesn't have any jobs to schedule or is done with all the schedules, after waiting for a minute, the scheduler process shuts down. Whenever a new job is added or there is any update to the existing jobs in `sys.jobs`, the launcher process starts again.
+
+EDB Job Schedule schedules the job only once based on the job runtime. If the same job needs to be rerun, then you need to feed the next job runtime. 
+
+All the recurring job scheduling is done through the `DBMS_SCHEDULER` and `DBMS_JOB` packages. For a recurring job, the next job runtime is added by these packages and not by `edb_job_scheduler`.
+
+`edb_job_scheduler` holds its meta data in two tables under the `sys` schema:
+
+- `jobs` — Holds information about the jobs to run.
+- `job_run_details` — Holds information about the job status. The status can be `'r' - running`, `'s' - success`, or `'f' - failure` for the respective `jobid`.
+
+
+The following are the columns in the `sys.job` table:
+
+```
+   Column   |           Type
+------------+--------------------------
+ jobid      | bigint
+ jobnextrun | timestamp with time zone
+ jobcommand | text
+ jobuser    | text
+```
+
+The following are the columns in the `sys.job_run_details` table:
+
+```
+    Column    |           Type
+--------------+--------------------------
+ jobid        | bigint
+ runid        | bigint
+ username     | text
+ workerpid    | integer
+ status       | character(1)
+ error        | text
+ scheduletime | timestamp with time zone
+ starttime    | timestamp with time zone
+ endtime      | timestamp with time zone
+```

advocacy_docs/pg_extensions/edb_job_scheduler/user_api.mdx

@@ -0,0 +1,12 @@
+---
+title: "User API"
+---
+
+The EDB Job Scheduler extension offers these API functions: 
+
+- `sys.reload_all_jobs` — Reloads all the unscheduled jobs from the current database. 
+
+  !!! Note
+     This function requests only the scheduler process. So, if the local storage of the scheduler limit meets the maximum set by `edb_job_scheduler.max_jobs_per_database`, loading fails. 
+
+- `sys.dump_schedule()` — Displays the current job schedule from the scheduler's local memory. The scheduler's local memory dumps all the jobs that weren't executed yet into the server log in JSON format. 

advocacy_docs/pg_extensions/index.mdx

@@ -3,12 +3,16 @@ title: "Postgres extensions available by deployment"
 navTitle: "Postgres extensions"
 hideToC: true
 navigation:
+    - "#All Postgres"
     - advanced_storage_pack
     - ldap_sync
     - pg_tuner
     - query_advisor
     - wait_states
     - pg_failover_slots
+    - "#EDB Postgres Advanced Server only"
+    - spl_check
+    - edb_job_scheduler
 ---
 
 Categories of extensions:

advocacy_docs/pg_extensions/index.mdx.in

@@ -3,12 +3,16 @@ title: "Postgres extensions available by deployment"
 navTitle: "Postgres extensions"
 hideToC: true
 navigation:
+    - "#All Postgres"
     - advanced_storage_pack
     - ldap_sync
     - pg_tuner
     - query_advisor
     - wait_states
     - pg_failover_slots
+    - "#EDB Postgres Advanced Server only"
+    - spl_check
+    - edb_job_scheduler
 ---
 
 Categories of extensions: