Re: Time to commit a change - Mailing list pgsql-performance

From Stephan Szabo
Subject Re: Time to commit a change
Date
Msg-id 20021212091233.H8927-100000@megazone23.bigpanda.com
Whole thread Raw
In response to Time to commit a change  (Ludwig Lim <lud_nowhere_man@yahoo.com>)
List pgsql-performance
On Wed, 11 Dec 2002, Ludwig Lim wrote:

>
> Hi:
>
>    How long does it take to commit a change to change
> to the database?
>
>    I'm currently developing a application where
> response time should be fast. Today I notice the
> following in my application log:
>
>   [12/10/2002     16:49:52] SQL statement created
>   [12/10/2002     16:49:58] Updating OK.
>
> The SQL statement is a just a stored procedure that
> insert a single row to a table. 6 seconds is quite a
> long time to execute an insert statement even if the
> table has referential integrity constrants and some
> triggers (the database is small, no tables having more
> than 100 rows). I tried to recreate the scenario by
> doing the following at a psql prompt:

Was this run while anything else was hitting the database
or just by itself?  I'd wonder if there were any lock
contentions (for example on foreign keys) or anything
like that which might have had some effect.


pgsql-performance by date:

Previous
From: "Shridhar Daithankar"
Date:
Subject: Re: Time to commit a change
Next
From: "Josh Berkus"
Date:
Subject: Re: Capping CPU usage?