> Thanks to some answers you gave me some time back, I've been doing some
> testing of PostgreSQL under BSD/OS-3.1 in preparation for a project that
> I'm working on. So far, it all seems to be working fine, apart from one
> (relatively minor) bug in psql -- it fails to close files it reads for a
> COPY command, meaning it can keep a multi-megabyte file open for days.
> The workaround is to do a new connect to the same database after the
> COPY, at which point the data file gets closed. Maybe you can get that
> fixed in a future release.
This is the first I have heard of this. The file commands/copy.c does
use a file descriptor cache, but that is really just used for allowing
more file opens that the OS permits. Actual opens and closes are
happending.
I assume the files you are talking about are the database table files.
Yes, they stay open because the backend may want to use them someday.
Is that a problem?
--
Bruce Momjian | 830 Blythe Avenue
maillist@candle.pha.pa.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)
