| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org mailing list" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Processing Delay |
| Date: | 2009-11-25 01:05:29 |
| Message-ID: | CA887F0D-4D50-4A2A-BF56-07FB93851AC9@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Nov 24, 2009, at 4:38 PM, Michael Lawson (mshindo) wrote:
> The problem we are encountering is a delay before we can read the
> updated value. This delay can be up to 15 seconds in some cases.
Is the delay a block (that is, you insert the value, and then the
SELECT that should retrieve it takes up to 15 seconds to execute), or
are you still seeing the old value for 15 seconds after the INSERT?
If the former, how heavily loaded is the database server, and what
does an EXPLAIN ANALYZE say about the SELECT?
If the latter, is the SELECT in the same or a different client
connection?
--
-- Christophe Pettus
xof(at)thebuild(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2009-11-25 01:30:28 | Re: pg_attribute.attnum - wrong column ordinal? |
| Previous Message | Konstantin Izmailov | 2009-11-25 01:03:03 | pg_attribute.attnum - wrong column ordinal? |