Re: Large number of open(2) calls with bulk INSERT into empty table - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Large number of open(2) calls with bulk INSERT into empty table
Date
Msg-id 8708.1345494466@sss.pgh.pa.us
Whole thread Raw
In response to Re: Large number of open(2) calls with bulk INSERT into empty table  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Large number of open(2) calls with bulk INSERT into empty table
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
>>> On the other hand, the problem of the FSM taking up 24kB for an 8kB
>>> table seems clearly worth fixing, but I don't think I have the cycles
>>> for it at present.  Maybe a TODO is in order.

> I certainly think that'd be worth a TODO.  Whether the rest of this is
> worth worrying about I'm not sure.

Surely we could just prevent creation of the FSM until the table has
reached at least, say, 10 blocks.

Any threshold beyond one block would mean potential space wastage,
but it's hard to get excited about that until you're into the dozens
of pages.
        regards, tom lane



pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: sha1, sha2 functions into core?
Next
From: Robert Haas
Date:
Subject: Re: Tab completion for DROP CONSTRAINT