From: | Michael Adler <adler(at)glimpser(dot)org> |
---|---|
To: | Pgsql-Cygwin <pgsql-cygwin(at)postgresql(dot)org> |
Subject: | Re: reproduced elusive cygwin bug |
Date: | 2002-01-16 16:28:05 |
Message-ID: | Pine.NEB.4.44.0201161126440.19719-100000@reva.sixgirls.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-cygwin |
On Wed, 16 Jan 2002, Tom Lane wrote:
> I said:
> > Hmm. But pg_internal.init is not held open, or shouldn't be. It
should
> > be read once and immediately closed during backend startup.
>
> Well damn. init_irels() forgets to close the file. Will fix for 7.2.
>
> Meanwhile, that still leaves us with a JDBC problem. Michael, will you
> report that to the pgsql-jdbc list?
Yes, I'll report as soon as I am granted access to that list. The
subscriber hasn't responded with a confirmation, however, after several
hours I started receiving the CYGWIN messages. I guess I'll shortly be on
th JDBC list.
It looks like the JDBC interfaces throws a nasty SQLexception when it
receives any NOTICE (or any message at that point which starts with "N").
I think that's a bug.
Mike Adler
From | Date | Subject | |
---|---|---|---|
Next Message | Jason Tishler | 2002-01-16 17:04:56 | Re: reproduced elusive cygwin bug |
Previous Message | Jason Tishler | 2002-01-16 16:08:56 | Re: reproduced elusive cygwin bug |