pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Question regarding blocking locks
3+ messages / 2 participants
[nested] [flat]

* Question regarding blocking locks
@ 2005-08-25 14:28 Kevin Keith <kevinrkeith@hotmail.com>
  2005-08-25 16:08 ` Re: Question regarding blocking locks Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 3+ messages in thread

From: Kevin Keith @ 2005-08-25 14:28 UTC (permalink / raw)
  To: pgsql-admin

I have a question regarding blocking locks in the pg database. I ran into a 
process which terminated abnormally, and to fully clear the locks it left 
behind I had to reboot the system (probably restarting postmaster would have 
had the same effect). This was a personal development system so this was no 
big deal to reboot it. I would like to know what other options I have so if 
this was to occur in a production environment in the future I had a less 
drastic measure to take to resolve the issue.

I saw the locks in the pg_locks view (the mode was Exclusivelock),

Can someone point me in the right direction to addressing such a problem 
should it occur in the future?

Thanks,

Kevin

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/




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

* Re: Question regarding blocking locks
  2005-08-25 14:28 Question regarding blocking locks Kevin Keith <kevinrkeith@hotmail.com>
@ 2005-08-25 16:08 ` Tom Lane <tgl@sss.pgh.pa.us>
  2005-08-26 11:59   ` Re: Question regarding blocking locks Kevin Keith <kevinrkeith@hotmail.com>
  0 siblings, 1 reply; 3+ messages in thread

From: Tom Lane @ 2005-08-25 16:08 UTC (permalink / raw)
  To: Kevin Keith <kevinrkeith@hotmail.com>; +Cc: pgsql-admin

"Kevin Keith" <kevinrkeith@hotmail.com> writes:
> I have a question regarding blocking locks in the pg database. I ran into a 
> process which terminated abnormally, and to fully clear the locks it left 
> behind I had to reboot the system (probably restarting postmaster would have 
> had the same effect).

Define "terminated abnormally".  You really aren't going to get helpful
answers without giving full details of what happened.  (If the
postmaster thought the backend had crashed, it would have forced a
database restart which would have wiped shared memory.  So it's not
clear from your comment what did happen.)

Also, exactly which PG version is this?

			regards, tom lane



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

* Re: Question regarding blocking locks
  2005-08-25 14:28 Question regarding blocking locks Kevin Keith <kevinrkeith@hotmail.com>
  2005-08-25 16:08 ` Re: Question regarding blocking locks Tom Lane <tgl@sss.pgh.pa.us>
@ 2005-08-26 11:59   ` Kevin Keith <kevinrkeith@hotmail.com>
  0 siblings, 0 replies; 3+ messages in thread

From: Kevin Keith @ 2005-08-26 11:59 UTC (permalink / raw)
  To: pgsql-admin

The version of Postgres is 7.4.

When I said the process had terminated abnormally - what I meant was a UNIX 
process (C program) had opened a database connection, run some updates 
without a COMMIT and then exited without closing the connection to the 
database or committing the transactions.



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


end of thread, other threads:[~2005-08-26 11:59 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-08-25 14:28 Question regarding blocking locks Kevin Keith <kevinrkeith@hotmail.com>
2005-08-25 16:08 ` Tom Lane <tgl@sss.pgh.pa.us>
2005-08-26 11:59   ` Kevin Keith <kevinrkeith@hotmail.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