| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Miguel Carvalho <miguel(at)ipatimup(dot)pt> |
| Cc: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Mysterious locking problem |
| Date: | 2002-05-21 19:22:15 |
| Message-ID: | 20020521121950.X19694-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 21 May 2002, Miguel Carvalho wrote:
> Hi,
>
> thank's for reppling.
>
> > Given your query things above I'm guessing you've turned on query
> > printing?
>
> Query print is off, because that will startve may hardisk verry quickly.
>
> > Are the selects perhaps SELECT ... FOR UPDATE queries going
>
> I forgot to mention that the selects are plain selects( not select for
> update ).
You might want to turn query printing on for just short time to see if
there are other queries being done. Do you have any foreign keys or
triggers on these tables that might be doing so?
> > for the same rows in which case I think the second would wait on the
> > first?
>
> Can this be a PHP issue?
Seems wierd for it to be.
Can you distill what you're doing into a small reproducable example and
send enough information to reproduce it?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2002-05-21 20:24:34 | Re: ERROR: value too long for type character varying(255) |
| Previous Message | Miguel Carvalho | 2002-05-21 18:38:51 | Re: Mysterious locking problem |