From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Frank Morton <fmorton(at)base2inc(dot)com>, Vadim Mikheev <vadim(at)krs(dot)ru>, pgsql-sql(at)hub(dot)org |
Subject: | Re: [SQL] Slow Inserts Again |
Date: | 1999-05-03 16:19:56 |
Message-ID: | 199905031619.MAA20460@candle.pha.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.
Yes, memory use it the place to look. We have had bugs in the past that
did not free memory, causing this problem.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Ross J. Reedstrom | 1999-05-03 17:01:31 | pg_dump bug (was Re: [SQL] Slow Inserts Again) |
Previous Message | Bruce Momjian | 1999-05-03 16:19:04 | Re: [SQL] No DIVIDE Operator |