No, that was a different problem related to recreating the
pg_internal.init file after a vacuum. This current leakage occurs
during normal usage.
-----Original Message-----
From: Henshall, Stuart - WCP
[mailto:SHenshall@westcountrypublications.co.uk]
Sent: Tuesday, February 05, 2002 11:49 AM
To: 'Tom Lane'; Tom Pfau
Cc: pgsql-bugs@postgresql.org; pgsql-cygwin@postgresql.org
Subject: RE: [CYGWIN] [BUGS] resource leak in 7.2
There was a cygwin postgresql 7.1.3-2 release to fix a file handle
problem
(init_rels() not closing pg_internal.init):
http://archives.postgresql.org/pgsql-cygwin/2002-01/msg00034.php
which refers to:
http://archives.postgresql.org/pgsql-cygwin/2002-01/msg00029.php
Maybe this is it?
- Stuart
> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: 05 February 2002 16:21
> To: Tom Pfau
> Cc: pgsql-bugs@postgresql.org; pgsql-cygwin@postgresql.org
> Subject: Re: [CYGWIN] [BUGS] resource leak in 7.2
>
>
> "Tom Pfau" <T.Pfau@emCrit.com> writes:
> > There was a bug in 7.1.2 that was fixed in 7.1.3 that may be back in
> > 7.2.
> > I downloaded 7.2 yesterday morning and started testing it.
> I left some
> > procedures running overnight performing random updates in a table.
> > Looking at task manager this morning, the three backend
> processes are
> > each consuming about 1.5e6 handles.
>
> I see nothing in the CVS logs to make me think that any
> file-handle-leakage
> bug was fixed between 7.1.2 and 7.1.3; and even less to make me think
> that 7.1.3 contains any fixes that weren't also applied to
> the 7.2 line.
>
> You're going to have to be a great deal more specific.
>
> regards, tom lane
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to
> majordomo@postgresql.org)
>