Hi all -
I'm doing some perf testing and need huge amounts of data. So I have a
program that is adding data to a few tables ranging from 500,000 to 15M
rows. The program is just a simply C# program that blasts data into the
DB, but after about 3M rows or so I get an errror:
ERROR: could not extend relation 1663/41130/41177: No space left on device
HINT: Check free disk space.
If I do a full VACUUM on the table being inserted into, the error goes
away but it comes back very quickly. Obviously, I wouldn't want this
happening in a production environment.
I've noticed some auto-vacuum settings as well (I just checked the box
and left all the defaults) but that doesn't seem to help too much.
What's the recommended setup in a production environment for tables
where tons of data will be inserted?
It seems to me there's some sort of "max table size" before you have to
allocate more space on the disk, however I can't seem to find where
these settings are and how to allow millions of rows to be inserted into
a table without having to vacuum every few million rows..
Mike
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
