Re: reproduced elusive cygwin bug - Mailing list pgsql-cygwin

From Tom Pfau
Subject Re: reproduced elusive cygwin bug
Date
Msg-id 5C47691674725C47B02996F02C0D362107B5C3@exchange.rane.net
Whole thread Raw
List pgsql-cygwin
Thanks.  I just rebuilt the server with the patch and preliminary test
show that it no longer causes problems after vacuums.  I'll do some more
testing today to make sure.

-----Original Message-----
From: Jason Tishler [mailto:jason@tishler.net]
Sent: Wednesday, January 16, 2002 12:05 PM
To: Tom Lane
Cc: Michael Adler; Tom Pfau; Pgsql-Cygwin
Subject: Re: reproduced elusive cygwin bug


Tom,

On Wed, Jan 16, 2002 at 11:02:06AM -0500, 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.

The attached patch (against Cygwin PostgreSQL 7.1.3-1) solves this
problem.  I will release 7.1.3-2 ASAP.

Jason

pgsql-cygwin by date:

Previous
From: Tom Lane
Date:
Subject: Re: reproduced elusive cygwin bug
Next
From: Frankinet Noël
Date:
Subject: Configure problem