From: Tom Lane <tgl@sss.pgh.pa.us>
To: Marc Morin <marc@sandvine.com>
Cc: Markus Schaber <schabi@logix-tt.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Decreasing BLKSZ
Date: Mon, 25 Sep 2006 18:27:26 -0400
Message-ID: <16132.1159223246@sss.pgh.pa.us> (raw)
In-Reply-To: <2BCEB9A37A4D354AA276774EE13FB8C20113068D@mailserver.sandvine.com>
References: <2BCEB9A37A4D354AA276774EE13FB8C20113068D@mailserver.sandvine.com>
"Marc Morin" <marc@sandvine.com> writes:
> No, an insert consists of roughly 10,000+ rows per transaction block.
Perhaps it would help to pre-sort these rows by key?
Like Markus, I'm pretty suspicious of lowering BLCKSZ ... you can try it
but it's likely to prove counterproductive (more btree index levels,
more rows requiring toasting, a tighter limit on what rows will fit at
all). I doubt I'd try to make it lower than a couple K in any case.
The bottom line here is likely to be "you need more RAM" :-(
I wonder whether there is a way to use table partitioning to make the
insert pattern more localized? We'd need to know a lot more about your
insertion patterns to guess how, though.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, marc@sandvine.com, schabi@logix-tt.com
Subject: Re: Decreasing BLKSZ
In-Reply-To: <16132.1159223246@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox