From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Steve Clark <sclark(at)netwolves(dot)com> |
Cc: | pgsql <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: ecpg program getting stuck |
Date: | 2008-03-21 16:08:21 |
Message-ID: | 23660.1206115701@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Steve Clark <sclark(at)netwolves(dot)com> writes:
> I have a program that worked fine in 7.4.19. I am in process of upgrading
> to 8.3.1 and my program runs for a while and then hangs. I used gdb
> to attach to the process and it shows the following backtrace which
> shows it
> going into the libpq library and getting stuck.
Well, gdb is lying to you to some extent (you'd probably get a better
backtrace if you had built libpq with debug symbols), but I think it's
simply waiting for a query response. Is the connected backend busy?
If the problem is that some query is taking way longer than you were
expecting, the first thought that comes to mind is "did you ANALYZE
your tables after reloading", and the second is "check for
configuration settings that you forgot to propagate into the new
installation".
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Edward Blake | 2008-03-21 16:15:05 | MySQL to Postgres question |
Previous Message | Edward Blake | 2008-03-21 16:06:47 | MySQL to Postgres question |