hi,
Dimitar Georgievski wrote, On 4/15/2004 23:07:
hi,
i'm running an update procedure on a table with approximately 100,000
records. The problem is the procedure is running endlessly even when the
update is very simple like in the following example:
update mytable
set client_id = 1
where mytabl
On Sat, 17 Apr 2004, Bruno Wolff III wrote:
> On Fri, Apr 16, 2004 at 12:47:58 -0500,
> Yudie <[EMAIL PROTECTED]> wrote:
> > Hi guys,
> > I would like to create a trigger that execute some programs,
> > is there a way to create a plpgsql function that execute shell command or
> > any other way t
On Fri, Apr 16, 2004 at 12:47:58 -0500,
Yudie <[EMAIL PROTECTED]> wrote:
> Hi guys,
> I would like to create a trigger that execute some programs,
> is there a way to create a plpgsql function that execute shell command or
> any other way to run a program?
> Thanks for your help.
Only untrusted
Hi guys,
I would like to create a trigger that execute some programs,
is there a way to create a plpgsql function that execute shell command or
any other way to run a program?
Thanks for your help.
Yudie
---(end of broadcast)---
TIP 2: you can get
Tom,
Yes. it looks like there was some locking condition in the database. in
the meantime it disappeared and the updates run quickly.
thanks for your help. this is the first time i'm working with PostgreSQL
and wasn't sure where to look for possible causes of the problem.
thanks,
dimitar
On T
Dimitar Georgievski <[EMAIL PROTECTED]> writes:
> the process under which the update is running reports among the usual
> process data "UPDATE waiting".
I don't think the UPDATE is doing anything at all --- that ps output
implies that it's waiting for some other backend to release an exclusive
loc
hi,
i'm running an update procedure on a table with approximately 100,000
records. The problem is the procedure is running endlessly even when the
update is very simple like in the following example:
update mytable
set client_id = 1
where mytable_id = 1
mytable_id is the primary key of mytable.
