From: | Steve Clark <sclark(at)netwolves(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: ecpg program getting stuck |
Date: | 2008-03-21 16:30:59 |
Message-ID: | 47E3E2C3.4060401@netwolves.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
> 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
>
>
Hi Tom,
I was testing with 8.2.6 before 8.3.0 came out and I don't think I saw
this problem.
I recompiled with debugging turned on and I'll do a closer inspection
when/if it happens
again.
Steve
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2008-03-21 16:33:05 | Re: deadlock error messages |
Previous Message | Rodrigo Gonzalez | 2008-03-21 16:29:51 | Re: MySQL to Postgres question |