pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedSET TIMEOUT equivalent / was: Lock timeout detection
2+ messages / 2 participants
[nested] [flat]
* SET TIMEOUT equivalent / was: Lock timeout detection
@ 2003-02-07 09:35 Christoph Haller <ch@rodos.fzk.de>
2003-02-07 10:31 ` Re: SET TIMEOUT equivalent / was: Lock timeout detection Tomasz Myrta <jasiek@klaster.net>
0 siblings, 1 reply; 2+ messages in thread
From: Christoph Haller @ 2003-02-07 09:35 UTC (permalink / raw)
To: pgsql-sql
>
> > >
> > > T1 (within psql):
> > > BEGIN; DELETE FROM <some_table> ;
> > > DELETE n
> > >
> > > T2 (within psql):
> > > BEGIN; DELETE FROM <some_table> ;
> > > <waiting forever>
> > >
> ...
> >
> > I don't think there is a deadlock in the example
> > given above. If I'm not mistaken a deadlock occurs if
> > both transactions are waiting for each other to
> > release the lock (i.e T1 waits for T2 to release
> > locks/resources while T2 is also waiting for T1 to
> > release locks/resources. In the above example, T1
> > doesn't wait for T2 to do something before finishes
> > the transaction (Only T2 is waiting for T1 to finish),
> > hence the condition for deadlock is not met.
> >
> Yupp, I agree.
> But from former DBMS I was dealing with,
> I know this SET TIMEOUT called feature, which if properly set
> terminated processes like that hanging on T2.
> Is there something comparable within Postgres?
>
Sorry to bother again with my question. Is it too stupid or
trivial to this list? Should I send it to NOVICE?
Regards, Christoph
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: SET TIMEOUT equivalent / was: Lock timeout detection
2003-02-07 09:35 SET TIMEOUT equivalent / was: Lock timeout detection Christoph Haller <ch@rodos.fzk.de>
@ 2003-02-07 10:31 ` Tomasz Myrta <jasiek@klaster.net>
0 siblings, 0 replies; 2+ messages in thread
From: Tomasz Myrta @ 2003-02-07 10:31 UTC (permalink / raw)
To: Christoph Haller <ch@rodos.fzk.de>; +Cc: pgsql-sql
Christoph Haller wrote:
> Sorry to bother again with my question. Is it too stupid or
> trivial to this list? Should I send it to NOVICE?
> Regards, Christoph
>
There are no stupid questions, there are only stupid answers ;-)
Anyway - try to not create more threads for the same subject if possible.
Regards,
Tomasz Myrta
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2003-02-07 10:31 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2003-02-07 09:35 SET TIMEOUT equivalent / was: Lock timeout detection Christoph Haller <ch@rodos.fzk.de>
2003-02-07 10:31 ` Tomasz Myrta <jasiek@klaster.net>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox