Skip site navigation (1) Skip section navigation (2)

Re: Large number of open(2) calls with bulk INSERT into empty table

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: 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: 2011-11-30 18:45:15
Message-ID: 25165.1322678715@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Yikes!  A table with 4 bytes of useful data is consuming 40kB on disk
> - 8kB in the main form, 8kB in the VM fork, and 24kB in the FSM fork.
> Ouch!

Yeah, ouch.  Why is the FSM fork eating so much space --- I'd have
expected 8k there, but 24?

Also, if VACUUM is going to cause the FSM to be created anyway, there
may not be a lot of point to refraining from creating the first page
right away.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2011-11-30 19:53:02
Subject: Re: autovacuum and default_transaction_isolation
Previous:From: Kevin GrittnerDate: 2011-11-30 18:34:37
Subject: Re: Reserved words and delimited identifiers

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group