> -Original Message-
> From: Tom Pfau
>
> I'm attaching two sql scripts in a zip file. Run script1.sql from one
> session. After it's done with the inserts, start script2.sql in another
> session. Have task manager running in the background and watch the
> backends eat handles.
I test
the table with an update
simultaneously.
-Original Message-
From: Jason Tishler [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 05, 2002 3:03 PM
To: Tom Lane
Cc: Tom Pfau; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [CYGWIN] [BUGS] resource leak in 7.2
On Tue, Feb 05, 2002 at 01:07:1
"Tom Pfau" <[EMAIL PROTECTED]> writes:
> In any case, if I run my test procedure which just performs updates to a
> random column of a random row of a 1000 row table, I can watch the
> handle usage continue to rise on the backend process.
> Looking a bit more closely now, a single process doesn't
nes are between 3 and 76 bytes.
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 05, 2002 11:21 AM
To: Tom Pfau
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [BUGS] resource leak in 7.2
"Tom Pfau" <[EMAIL PROTECTED]> writes:
> There was a
; Tom Pfau
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
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 refer
"Henshall, Stuart - WCP" <[EMAIL PROTECTED]> writes:
> There was a cygwin postgresql 7.1.3-2 release to fix a file handle problem
> (init_rels() not closing pg_internal.init):
> Maybe this is it?
No, because (a) that problem is also fixed in 7.2, and (b) that was
only responsible for leaking one
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]]
> Sent: 05 February 2002 16:21
> To: Tom Pfau
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: [CYGWIN] [BUGS] resource leak in 7.2
>
>
> "Tom Pfau" <[EMAIL PROTECTED]> wr
"Tom Pfau" <[EMAIL PROTECTED]> 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
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
