From: | Doug McNaught <doug(at)wireboard(dot)com> |
---|---|
To: | Aaron Brashears <gila(at)gila(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: big pg 6.5 and 7.1 problem in simple application |
Date: | 2001-05-02 20:22:06 |
Message-ID: | m3vgnjmrgx.fsf@belphigor.mcnaught.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Aaron Brashears <gila(at)gila(dot)org> writes:
> We have a simple ad tracking application, which has a (mostly) fixed
> table size where each row represents a particular ad. We have about 70
> rows in the database and use php scripts in apache which connect over
> odbc, read a single row, increment a counter, and update that
> row. We're performing about 30 updates a second and after a few
> minutes the postmaster either hangs or dumps core.
I'd try compiling 7.1 with debugging enabled, and do a GDB backtrace
on your core dumps. Otherwise it's hard to help you.
-Doug
--
The rain man gave me two cures; he said jump right in,
The first was Texas medicine--the second was just railroad gin,
And like a fool I mixed them, and it strangled up my mind,
Now people just get uglier, and I got no sense of time... --Dylan
From | Date | Subject | |
---|---|---|---|
Next Message | Albertson, Chris | 2001-05-02 20:41:30 | "group by" is quite expensive |
Previous Message | Joel Burton | 2001-05-02 20:21:50 | Re: best way to implement producer/consumer in Perl |