FW: [PERFORM] Deadlock Issue with PostgreSQL
Hello Tom, Thanks a lot for your quick response. Which version do you think is the more stable one that we should upgrade to? Please provide us with the Upgrade instructions/documentation to be followed for both red hat and PostgreSQL. Thanks and Best Regards, Anu -Original Message- From: Tom Lane [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 21, 2005 12:15 PM To: Anu Kucharlapati Cc: pgsql-performance@postgresql.org; Owen Blizzard Subject: Re: [PERFORM] Deadlock Issue with PostgreSQL Anu Kucharlapati [EMAIL PROTECTED] writes: Red Hat Linux release 7.3 Apache 1.3.20 PostgreSQL 7.1.3 I'm not sure about Apache, but both the RHL and Postgres versions you are using are stone age --- *please* update. Red Hat stopped supporting that release years ago, and the PG community isn't supporting 7.1.* anymore either. There are too many known problems in 7.1.* that are unfixable without a major-version upgrade. regards, tom lane
Re: FW: [PERFORM] Deadlock Issue with PostgreSQL
Anu, Thanks a lot for your quick response. Which version do you think is the more stable one that we should upgrade to? 8.0.3 Please provide us with the Upgrade instructions/documentation to be followed for both red hat and PostgreSQL. See the PostgreSQL documentation for upgrade instructions. Given how old your version is, you might need to go through an intermediate version, like 7.3. Red Hat upgrades are between you and Red Hat. They sell support for a reason ... -- --Josh Josh Berkus Aglio Database Solutions San Francisco ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[PERFORM] Deadlock Issue with PostgreSQL
Background: We are running a web application on apache with database server as PostgreSQL. The application is a expense claim application with workflow. The software versions are specified below: Red Hat Linux release 7.3 Apache 1.3.20 PostgreSQL 7.1.3 Problem: When the application is accessed by many users like say 40, the PostgreSQL database freezes. Description of Process happening behind: The application mainly puts load on one table (worklist) where the steps were created for each expense claim initiated. While creating each step for claim there is exclusive row lock and at the end inserts a new step. Both these statements are in one transaction. When the apache hangs in between the deadlock remains. In this way there are many deadlocks created which makes the database to finally freeze. To resolve this we were restarting the PostgreSQl db. Sometime the apache also hangs. Then we were restarting the apache. There is no log created in postgreSQL. Whereas our application records an error log: Failed to gain exclusive table row lock We were guessing that the database hanging is due to deadlock issue. But not sure of it. I have attached the postgreSQL.conf file for your reference to check the settings. Please let me know what might be the reason and how to check and resolve it. Thanks and Best Regards, Anu postgresql.conf Description: postgresql.conf ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [PERFORM] Deadlock Issue with PostgreSQL
Anu Kucharlapati [EMAIL PROTECTED] writes: Red Hat Linux release 7.3 Apache 1.3.20 PostgreSQL 7.1.3 I'm not sure about Apache, but both the RHL and Postgres versions you are using are stone age --- *please* update. Red Hat stopped supporting that release years ago, and the PG community isn't supporting 7.1.* anymore either. There are too many known problems in 7.1.* that are unfixable without a major-version upgrade. regards, tom lane ---(end of broadcast)--- TIP 6: explain analyze is your friend
