PostgreSQL Bugs

Collected from the PG bugs email list.

Bug ID15880
PG Version11.3
OSCentOS Linux release 7.6.1810 (Core)
Opened2019-06-28 10:00:52+00
Reported byShiwangini Shishulkar

Body of first available message related to this bug follows.

The following bug has been logged on the website:

Bug reference:      15880
Logged by:          Shiwangini Shishulkar
Email address:      (redacted)
PostgreSQL version: 11.3
Operating system:   CentOS Linux release 7.6.1810 (Core)

To implement scheduling, we need use pgagent. For that, extension from
And unzipped it to the location, from where it picks. Now, connected to  sql
prompt as tried to create extension as per below:

[root@localhost pgAgent-4.0.0-Source]# su - postgres -c "psql"
psql (11.3)
Type "help" for help.

postgres=# \c postgres
You are now connected to database "postgres" as user "postgres".
postgres=# CREATE EXTENSION pgagent;
ERROR:  extension "pgagent" has no installation script nor update path for

The last line error message i received which i'm not able to interpret.
Could you please help me with this. Any help will be appreciated. Also, if
there is any another way to configure/use pgagent then please share us the
link of doc.


2019-06-28 10:00:52+00PG Bug reporting formBUG #15880: ERROR: could not open extension control file "/usr/pgsql-11/share/extension/pgagent.control": No su
2019-06-28 14:25:40+00Tom LaneRe: BUG #15880: ERROR: could not open extension control file "/usr/pgsql-11/share/extension/pgagent.control": No su