From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Florian Weimer <fweimer(at)bfk(dot)de>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Large number of open(2) calls with bulk INSERT into empty table |
Date: | 2012-08-20 20:47:40 |
Message-ID: | CA+Tgmoa=9k4DSOOtX3rx5hudCSOOBQnqFaVu2kRoO9r5djW2Jw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Aug 20, 2012 at 4:27 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)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.
I dunno, I think one-row tables are pretty common.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2012-08-20 20:50:54 | Re: NOT NULL constraints in foreign tables |
Previous Message | Robert Haas | 2012-08-20 20:46:45 | Re: "CLUSTER VERBOSE" tab completion |