Postgres Pro
Downloads
Home   >   mailing lists

Re: [PGAGENT] Upgrade pgAgent from unpackaged version - Mailing list pgadmin-hackers

From Rushabh Lathia
Subject Re: [PGAGENT] Upgrade pgAgent from unpackaged version
Date
Msg-id CAMBO3tUqYuONeAzs4YStKvj4etSDKD0xKKvU=xSMA-7-9yGCMQ@mail.gmail.com
Whole thread Raw
In response to Re: [PGAGENT] Upgrade pgAgent from unpackaged version  (Dave Page <dpage@pgadmin.org>)
Responses Re: [PGAGENT] Upgrade pgAgent from unpackaged version  (Dave Page <dpage@pgadmin.org>)
List pgadmin-hackers
Tree view
Thanks Ashesh and Dave.

I verified the changes and it looks good to me.  I found that newly
added unpackaged file still have old file header comment.  Which
require change with new file name.

PFA patch to fix the same.

Thanks,


On Wed, Jun 13, 2018 at 6:10 PM, Dave Page <dpage@pgadmin.org> wrote:
Thanks, applied.

On Wed, Jun 13, 2018 at 5:11 AM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
Hi Dave,

As per my conversation with Rushabh, we need to rename the pgagent--unpackaged--3.4.sql to pgagent--unpackaged--4.0.sql as it the current version has changed. We also need to update the schema version function for the unpackaged extension.

Please find the attached patch for the same.

--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company


http://www.linkedin.com/in/asheshvashi




--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



--
--
Rushabh Lathia
Database Architect
EnterpriseDB Corporation
The Enterprise Postgres Company

Phone: +91-20-30589494

Website: http://www.enterprisedb.com
EnterpriseDB Blog: http://blogs.enterprisedb.com/
Follow us on Twitter: http://www.twitter.com/enterprisedb

Attachment

pgadmin-hackers by date:

Previous
From: pgAdmin 4 Jenkins
Date:
Subject: Jenkins build is back to normal : pgadmin4-master-python27 #646
Next
From: Khushboo Vashi
Date:
Subject: [pgAdmin4][Patch]: RM #3411 - pgAdmin 4, Mac. The application servercould not be contacted