From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | andres mackiewicz <mackiew(at)seciu(dot)edu(dot)uy> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: DBD::Pg::st execute failed: ERROR |
Date: | 2000-10-26 15:12:04 |
Message-ID: | Pine.BSF.4.10.10010260809120.26411-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
It seems like postgres is thinking that the query is incorrectly
formatted. Do you know what query is being run when this happens?
You may wish to start the postmaster with -d2 which should print
out the queries that postgres is seeing.
Stephan Szabo
sszabo(at)bigpanda(dot)com
On Wed, 25 Oct 2000, andres mackiewicz wrote:
> I have this problem:
> The next message appears when I try to make an INSERT into a table:
>
>
> Connection refused
> DBD::Pg::st execute failed: ERROR:
> parser: parse error at or near "refused"
>
>
> The situation is the next: I have a lot of processes making insertions
> in the same database, and I suspect that is the cause of the message,
> but I'm not sure.
>
> Could be another cause?
> How can I solve it?
>
> I have tried the "autocommit" option on, and i still have the
> problem.
>
> Thank you.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-10-26 15:42:11 | Idea: cross-check versions during initdb |
Previous Message | Tom Lane | 2000-10-26 15:05:01 | Re: sanity of using -current? |