From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
---|---|
To: | "Carl M(dot) Nasal II" <cnasal(at)bmaenterprises(dot)com> |
Cc: | Ian Barwick <barwick(at)gmail(dot)com>, pgsql general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL Server Crash using plPHP or PL/Perl |
Date: | 2006-07-12 18:36:46 |
Message-ID: | 1152729406.14241.29.camel@state.g2switchworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 2006-07-12 at 07:32, Carl M. Nasal II wrote:
> I apologize for not including the server information in the last e-mail. I
> knew I would forget something. :)
>
> PostgreSQL 8.1.4 (compiled from source)
> Debian GNU/Linux 3.1
> Intel(R) Pentium(R) D CPU 3.00GHz
> 1GB RAM
>
> We have not be able to test the triggers anywhere else that has any load on
> it. If we run it on a test set of data, it works fine because it is not
> being hit by that many users. However, if we disable the triggers,
> everything on the live server appears to work fine and PostgreSQL never dies.
>
> Also, we are using the PostgreSQL ODBC driver from a Windows application we
> have developed. It seems that if the user tries to access the server while
> it restarts after this error, they get an error. However, if the user is
> not doing anything when the server restarts and then tries to access data
> later, it appears to automatically do the reconnect and everything is fine.
a poor man's way to apply lots of parallel load is to build a few web
pages that can individually apply a bit of load, and use apache's ab
program to beat on the web server and, by extension, the database.
From | Date | Subject | |
---|---|---|---|
Next Message | Joseph Shraibman | 2006-07-12 18:54:54 | Re: VACUUM FULL versus CLUSTER ON |
Previous Message | Scott Marlowe | 2006-07-12 18:34:25 | Re: doesn't recognize "!=-" (not equal to a negative |