I ran into something like this once, where a complex update occurred inside a
transaction. When the update happened, I saw what you describe - the DB hung,
and the load average shot out thru the roof until I restarted the PG daemon.
The query otherwise worked fine, but only failed with this spec
On Tue, 2005-10-25 at 13:14 -0700, Kishore B wrote:
> Hi ,
> I am Kishore doing freelance development of J2EE applications.
>
>
> We switched to use Postgresql recently because of the advantages it
> has over other commercial databases. All went well untill recently,
> untill we began working
