Vatsal Avasthi <[EMAIL PROTECTED]> writes:
> I am using postgres version 7.2.1.
> Looks like both try to have a lock and that leads to a deadlock
> situation.
It's hard to believe that SELECT and DROP TRIGGER alone could deadlock;
and if they did, you should get a deadlock failure report, not an
On 30 Oct 2003, Vatsal Avasthi wrote:
>
> Hi,
> I am facing a strange problem and thats bugging me for a long time,
> I am using postgres version 7.2.1.
Is it possible for you to upgrade to 7.2.4 just to make sure it's not a
problem that was fixed from 7.2.1 to 7.2.4?
--
Hi,
I am facing a strange problem and thats bugging me for a long time,
I am using postgres version 7.2.1.
I have written an application in C which tries to drop a trigger and simultaneously read from a table thats has data related to that trigger.
the whole database comes into a deadl
Christopher Kings-Lynne wrote:
> I'm always getting deadlocks like this:
>
> [30-Mar-2003 19:19:51] PHP Fatal error: postgres7 error: [0: ERROR:
> deadlock detected
> ] in EXECUTE("INSERT INTO users_foods (user_id, date, meal_id, quantity,
> eaten, food_id) VALUES ('55283', '2003-04-07', '1', '1.
On Mon, 31 Mar 2003, Christopher Kings-Lynne wrote:
> I'm always getting deadlocks like this:
>
> [30-Mar-2003 19:19:51] PHP Fatal error: postgres7 error: [0: ERROR:
> deadlock detected
> ] in EXECUTE("INSERT INTO users_foods (user_id, date, meal_id, quantity,
> eaten, food_id) VALUES ('55283',
Christopher Kings-Lynne wrote:
> I'm always getting deadlocks like this:
>
> [30-Mar-2003 19:19:51] PHP Fatal error: postgres7 error: [0: ERROR:
> deadlock detected
> ] in EXECUTE("INSERT INTO users_foods (user_id, date, meal_id, quantity,
> eaten, food_id) VALUES ('55283', '2003-04-07', '1', '1.
I'm always getting deadlocks like this:
[30-Mar-2003 19:19:51] PHP Fatal error: postgres7 error: [0: ERROR:
deadlock detected
] in EXECUTE("INSERT INTO users_foods (user_id, date, meal_id, quantity,
eaten, food_id) VALUES ('55283', '2003-04-07', '1', '1.00', 'f', '779')")
in /usr/local/www/gener
