From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Frank Morton" <fmorton(at)base2inc(dot)com> |
Cc: | "Vadim Mikheev" <vadim(at)krs(dot)ru>, pgsql-sql(at)hub(dot)org |
Subject: | Re: [SQL] Slow Inserts Again |
Date: | 1999-05-03 14:42:52 |
Message-ID: | 19916.925742572@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
>> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Bitmead | 1999-05-03 15:02:32 | Re: [SQL] No DIVIDE Operator |
Previous Message | Joerg Fischer | 1999-05-03 14:35:30 | Re: [SQL] No DIVIDE Operator |