From: Tom Lane <tgl@sss.pgh.pa.us>
To: Frank Morton <fmorton@base2inc.com>
Cc: Vadim Mikheev <vadim@krs.ru>
Cc: pgsql-sql@hub.org
Subject: Re: [SQL] Slow Inserts Again
Date: Mon, 03 May 1999 10:42:52 -0400
Message-ID: <19916.925742572@sss.pgh.pa.us> (raw)
In-Reply-To: <06c001be956b$e35db0c0$8355e5ce@base2inc.com>
>> Why _each_?
>> Enclose ALL statements by begin; & end; to insert ALL data
>> in SINGLE transaction:
But the transaction boundaries wouldn't have anything to do with
Frank's real problem, which is that the insertions are getting
slower and slower. There's no good reason for that; and other
people are not reporting any comparable problems. (Considering
that we *have* been getting trouble reports for more-than-2-gig
tables, it's clear that people are putting large amounts of data
into 6.5; so it's not like Frank is stressing the system more
than it has been before.)
Frank, what does the memory usage of the backend that's processing
this insertion look like; has it been growing steadily? I'm wondering
whether you could have a problem with poor malloc behavior, or some
such.
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, fmorton@base2inc.com, vadim@krs.ru, pgsql-sql@hub.org
Subject: Re: [SQL] Slow Inserts Again
In-Reply-To: <19916.925742572@sss.pgh.pa.us>
References: <06c001be956b$e35db0c0$8355e5ce@base2inc.com> <19916.925742572@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