From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | gjb(at)acm(dot)org (Greg Black) |
Cc: | hackers(at)postgreSQL(dot)org |
Subject: | Re: PostgreSQL under BSD/OS |
Date: | 1998-08-29 18:16:46 |
Message-ID: | 199808291816.OAA10942@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
We have a 6.4 beta starting September 1, with final October 1. It is
possible that somehow there is a problem with 6.3.2 that I am not seeing
in the current sources. The new code that closes a file descriptor left
open from a failed COPY will be in there, so you should try that release
first.
> > OK, in pgsql/src/backend/command/copy.c, you should see a function call
> > to FreeFile(). That is what is supposed to be called to free the open
> > file. AllocateFile opens the file a few lines above it, in either read
> > or write mode.
> >
> > If you can, can you put a little printf statement just before the
> > FreeFile, and see if it is getting called. You have to look in the
> > postmaster log file to see the output of the printf(). If it is getting
> > called, I have no idea why it would still be holding the file
> > descriptor. If it is not calling that function, I am confused because I
> > can't see how it could get out of that function without calling it.
>
> I'm willing to have a look at this in a few weeks, but I don't have time
> to do it now. I'll get back to you when I've got some additional info.
>
> --
> Greg Black <gjb(at)acm(dot)org>
>
>
>
--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)
From | Date | Subject | |
---|---|---|---|
Next Message | Keith Parks | 1998-08-29 18:29:04 | Core dump in regression tests. |
Previous Message | Bruce Momjian | 1998-08-29 18:09:07 | Re: [DOCS] Re: [HACKERS] vacuum problem |