Hi Dave/Guillaume, Please find the attached patch to resolve this issue. In the following commit - the file was modified and we were not able to spot the issue earlier. a265fb2977253fce436e276320d337425639384c
It can be applied to both branches - REL-1_14_0_PATCHES & master. -- Thanks & Regards, Ashesh Vashi EnterpriseDB INDIA: Enterprise PostgreSQL Company<http://www.enterprisedb.com> *http://www.linkedin.com/in/asheshvashi*<http://www.linkedin.com/in/asheshvashi> On Fri, Jun 8, 2012 at 3:26 PM, Ashesh Vashi <ashesh.va...@enterprisedb.com>wrote: > On Fri, Jun 8, 2012 at 3:23 PM, Michal Kozusznik < > kozusznik.mic...@ifortuna.cz> wrote: > >> Hello >> We have found this issue while working with postgresql 8.4 >> pgAdmin run under Windows7 64bit. Confirmed by all guys working with >> pgAdmin 1.14.3 on Win7 (others are working with older ver of pgAdmin) >> > Thanks for the report. > Looks like - I break it. > I was trying to resolve a bug for PostgreSQL 9.2. > > Will work on it as soon as possible. > > > -- > > Thanks & Regards, > > Ashesh Vashi > EnterpriseDB INDIA: Enterprise PostgreSQL > Company<http://www.enterprisedb.com/> > > > *http://www.linkedin.com/in/asheshvashi* > >> >> >> Dne 8.6.2012 11:49, Ashesh Vashi napsal(a): >> >> Hi Michal, >> >> Can you please tell us, on which database server have connected through >> pgAdmin3? >> >> >> >> >
Default_value_pg-8.4.patch
Description: Binary data
-- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
