Re: [HACKERS] DROP TABLE leaks file descriptors

Tom, is this resolved?

> I have just finished characterizing a nasty little bug in table
> destruction. Do this:
> create table x (i int4);
> create index xindex on x (i);
> drop table x;
> The backend will now have one more open file than it had before
> (use lsof or similar tool to check). Repeat enough times, and
> the backend crashes for lack of file descriptors.
>
> It appears that the file that is left open is the index relation.
> The index is *not* open at the end of the CREATE INDEX command;
> apparently, DROP TABLE opens the index for some reason, and then
> forgets to close the file descriptor when it destroys the index.
>
> Create more than one index, and they're *all* held open after DROP.
>
> I see the same behavior in both 6.4.2 and 6.5-current.
>
> Does anyone have a good idea where to look for the resource leak?
> I've never looked at table creation/destruction...
>
> regards, tom lane
>
>

--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026