From: | Dinesh Kumar <dinesh(dot)kumar(at)enterprisedb(dot)com> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | Sven Meirsman <sven(dot)meirsman(at)gmail(dot)com>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>, pgAdmin Support <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: [pgadmin-support] pgAdmin 1.18.0 + slony-I 2.2.0 + PG 9.3 |
Date: | 2014-02-07 09:28:48 |
Message-ID: | CAKWsr7jm=E6_UpfXUpVzvhCw4jZiSZviWSQ734++PXnem6GoMg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers pgadmin-support |
Hi Dave/Team,
I would like to take the ownership of this patch from now onwards.
Sorry for my previous test case result, which is an improper one from my
side. I believe, i need to configure the same slony version on PG 9.2 as
well. It seems an expected behaviour if the slony version is not match.
And also i have fixed one small version bug as below.
BUG Details
------------------
After configuring the slony on PG 9.2 server follow the below steps.
1. Launch pgadmin III
2. Add New server and Right Click on Slony cluster node
3. Click on Restart node
4. Error occurred regarding procpid does not exist.
ERROR: column sa.procpid does not exist
LINE 1: .. nl, pg_stat_activity sa WHERE nl.nl_backendpid = sa.procpid.
I have fixed this trivial bug on top of Neel's patch, and sending single
patch for these two issues.
Kindly let me know, if i miss anything here.
Thanks in advance.
Regards,
Dinesh
Attachment | Content-Type | Size |
---|---|---|
Slony_Fix_V2.patch | application/octet-stream | 12.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2014-02-08 17:19:05 | debugger.c tries to set log_min_messages, why? |
Previous Message | Dave Page | 2014-02-07 09:15:11 | Re: Fixed some compiler warnings |
From | Date | Subject | |
---|---|---|---|
Next Message | Muhammad Rizwan Anwar | 2014-02-07 10:08:49 | Re: Restoring PostgreSQL Database Backup |
Previous Message | Craig Ringer | 2014-02-07 04:26:35 | Re: Restoring PostgreSQL Database Backup |