From: | Eric Lee Green <eric(at)badtux(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Doug McNaught <doug(at)wireboard(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Performance issues |
Date: | 2002-03-19 15:08:54 |
Message-ID: | 200203190958.59922@badtux.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Monday 18 March 2002 11:21 pm, Tom Lane wrote:
> Doug McNaught <doug(at)wireboard(dot)com> writes:
> > So just te be clear, what you're seeing is that batched INSERTs go
> > fast, and batched SELECTs go fast, but when you interleave them it's
> > really slow?
> > If you can provide a test case, I'm
> > willing to bet the PG gurus will be interested...
>
> Yup, I'd be interested in a test case. This behavior makes no sense
> to me either :-(
GRRR! I wrote a quicky test program that bypasses the transaction processing
and just logs or skips the file. I can skip already-inserted files at
approximately 1,000 records per second, and insert new files into the
database at approximately 300 records per second.
It's obvious that I'm not having a PostgreSQL problem. I'm beginning to think
I have an interaction with a $^%(at)#$% piece of crap commercial device driver
installed on the system.
I thank you for your kind responses anyhow, even though it didn't turn out to
be a PostGreSQL problem.
-- Eric
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-03-19 15:18:32 | Re: multiple counts using CASE |
Previous Message | Johnson, Shaunn | 2002-03-19 14:06:31 | multiple counts using CASE |