[pgadmin-hackers] pgAdmin III commit: Modified the CHANGELOG for previous commit (46363d9

2014-01-28 Thread Ashesh Vashi
Modified the CHANGELOG for previous commit (46363d95f19ce35babd9e3b27bfdcacfa298caf8) Branch -- REL-1_18_0_PATCHES Details --- http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=e9561cbf271e01c162bf1e305f01b16924ac8a12 Modified Files -- CHANGELOG |2 ++ 1 file

[pgadmin-hackers] pgAdmin III commit: Flush the changes in the settings as soon as new se

2014-01-28 Thread Ashesh Vashi
Flush the changes in the settings as soon as new server is added [Kaarel Moppel] (cherry picked from commit ea21706e569e80b679d068b087408a1fc193cc70) Branch -- REL-1_18_0_PATCHES Details --- http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=46363d95f19ce35babd9e3b27bfdcacfa2

[pgadmin-hackers] pgAdmin III commit: Changed the CHANGELOG as the fix - 'Saving the chan

2014-01-28 Thread Ashesh Vashi
Changed the CHANGELOG as the fix - 'Saving the changes in settings as soon as new server is added', is also applied in the 'REL-1_18_0_PATCHES' branch too. Branch -- master Details --- http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=d747f97ac1d4fb54a223b857e58df497d43fd011

Re: [pgadmin-hackers] Add CREATE EXTENSION Support

2014-01-28 Thread David E. Wheeler
On Jan 17, 2014, at 10:50 AM, David E. Wheeler wrote: > I think this is a relatively clean way to go. I'm wondering, though, whether > the extension will be needed on PostgreSQL servers where pgAgent itself isn't > installed. Might it be worthwhile to also release an extension that just > cont