pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
commit after dead lock
4+ messages / 3 participants
[nested] [flat]

* commit after dead lock
@ 2004-01-30 00:25 Gaetano Mendola <mendola@bigfoot.com>
  2004-01-30 01:11 ` Re: commit after dead lock Stephan Szabo <sszabo@megazone.bigpanda.com>
  0 siblings, 1 reply; 4+ messages in thread

From: Gaetano Mendola @ 2004-01-30 00:25 UTC (permalink / raw)
  To: pgsql-admin

Hi all,
is it normal that postgres dont complain
doing a commit after a deadlock ?

kalman=# select * from test where a = 5 for update;
ERROR:  deadlock detected
DETAIL:  Process 4144 waits for ShareLock on transaction 40180; blocked 
by process 4141.
Process 4141 waits for ShareLock on transaction 40181; blocked by 
process 4144.
kalman=# commit;
COMMIT
kalman=#


Regards
Gaetano Mendola




^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: commit after dead lock
  2004-01-30 00:25 commit after dead lock Gaetano Mendola <mendola@bigfoot.com>
@ 2004-01-30 01:11 ` Stephan Szabo <sszabo@megazone.bigpanda.com>
  2004-01-30 03:50   ` Re: commit after dead lock Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 4+ messages in thread

From: Stephan Szabo @ 2004-01-30 01:11 UTC (permalink / raw)
  To: Gaetano Mendola <mendola@bigfoot.com>; +Cc: pgsql-admin


On Fri, 30 Jan 2004, Gaetano Mendola wrote:

> Hi all,
> is it normal that postgres dont complain
> doing a commit after a deadlock ?
>
> kalman=# select * from test where a = 5 for update;
> ERROR:  deadlock detected
> DETAIL:  Process 4144 waits for ShareLock on transaction 40180; blocked
> by process 4141.
> Process 4141 waits for ShareLock on transaction 40181; blocked by
> process 4144.
> kalman=# commit;
> COMMIT

It's not really any different than other errors. The commit doesn't
complain (although it also doesn't actually commit anything).

sszabo=# begin;
BEGIN
sszabo=# select * from foo;
ERROR:  relation "foo" does not exist
sszabo=# commit;
COMMIT




^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: commit after dead lock
  2004-01-30 00:25 commit after dead lock Gaetano Mendola <mendola@bigfoot.com>
  2004-01-30 01:11 ` Re: commit after dead lock Stephan Szabo <sszabo@megazone.bigpanda.com>
@ 2004-01-30 03:50   ` Tom Lane <tgl@sss.pgh.pa.us>
  2004-01-30 09:47     ` Re: commit after dead lock Gaetano Mendola <mendola@bigfoot.com>
  0 siblings, 1 reply; 4+ messages in thread

From: Tom Lane @ 2004-01-30 03:50 UTC (permalink / raw)
  To: Stephan Szabo <sszabo@megazone.bigpanda.com>; +Cc: Gaetano Mendola <mendola@bigfoot.com>; pgsql-admin

Stephan Szabo <sszabo@megazone.bigpanda.com> writes:
> It's not really any different than other errors. The commit doesn't
> complain (although it also doesn't actually commit anything).

People have occasionally suggested that the command tag from a COMMIT
should read "ABORT" or "ROLLBACK" if the transaction was previously
aborted.  I don't have a strong feeling about it one way or the other.
It'd clearly be helpful for human users, but I could see it confusing
programs that expect the existing behavior of command tag always
matching command.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: commit after dead lock
  2004-01-30 00:25 commit after dead lock Gaetano Mendola <mendola@bigfoot.com>
  2004-01-30 01:11 ` Re: commit after dead lock Stephan Szabo <sszabo@megazone.bigpanda.com>
  2004-01-30 03:50   ` Re: commit after dead lock Tom Lane <tgl@sss.pgh.pa.us>
@ 2004-01-30 09:47     ` Gaetano Mendola <mendola@bigfoot.com>
  0 siblings, 0 replies; 4+ messages in thread

From: Gaetano Mendola @ 2004-01-30 09:47 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; pgsql-admin

Tom Lane wrote:

> Stephan Szabo <sszabo@megazone.bigpanda.com> writes:
> 
>>It's not really any different than other errors. The commit doesn't
>>complain (although it also doesn't actually commit anything).
> 
> 
> People have occasionally suggested that the command tag from a COMMIT
> should read "ABORT" or "ROLLBACK" if the transaction was previously
> aborted.  I don't have a strong feeling about it one way or the other.
> It'd clearly be helpful for human users, but I could see it confusing
> programs that expect the existing behavior of command tag always
> matching command.


Well, I agree but I think that is better at least rise a
warning.


regards
Geetano Mendola




^ permalink  raw  reply  [nested|flat] 4+ messages in thread


end of thread, other threads:[~2004-01-30 09:47 UTC | newest]

Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-01-30 00:25 commit after dead lock Gaetano Mendola <mendola@bigfoot.com>
2004-01-30 01:11 ` Stephan Szabo <sszabo@megazone.bigpanda.com>
2004-01-30 03:50   ` Tom Lane <tgl@sss.pgh.pa.us>
2004-01-30 09:47     ` Gaetano Mendola <mendola@bigfoot.com>

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