Skip site navigation (1) Skip section navigation (2)

Re: Time to commit a change

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: Ludwig Lim <lud_nowhere_man(at)yahoo(dot)com>
Cc: PostgreSQL Mailing list <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Time to commit a change
Date: 2002-12-12 17:15:43
Message-ID: (view raw, whole thread or download thread mbox)
Lists: 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.

In response to

pgsql-performance by date

Next:From: Josh BerkusDate: 2002-12-12 17:43:25
Subject: Re: Capping CPU usage?
Previous:From: Shridhar DaithankarDate: 2002-12-12 08:07:34
Subject: Re: Time to commit a change

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group