| From: | "Kevin Keith" <kevinrkeith(at)hotmail(dot)com> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Question regarding blocking locks |
| Date: | 2005-08-25 14:28:13 |
| Message-ID: | BAY108-F30AE11762B669A5598C02BB9AB0@phx.gbl |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Browne | 2005-08-25 14:54:11 | Re: size of indexes and tables (more than 1GB) |
| Previous Message | Bruno Wolff III | 2005-08-25 13:23:34 | Re: size of indexes and tables (more than 1GB) |