Обсуждение: backend stalls
Hi I'm tearing my hair out here, the backend seems to randomly decide to stall and not serve any more queries (processes are listed as waiting). It happens on all sorts of queries (including CREATE TABLE and CREATE INDEX). I have completely uninstalled and deleted the whole installation and reinstalled - only to have it do it again mid way through entering the SQL to rebuild my database (not a big one ~25 tables, and no rows to speak of - havent got that far yet). I was thinking corrupted tables - or corrupt system catalog, but even vacuumdb stalls as well... Any help would be appreciated, I have so much work to do and I cant do anything without the database working :( My install is Postgres 7.0.3-8 from the RedHat RPMs runing on RH7.1 I know I havent given much specific information, I dont really know where to start. What its doing at this very minute is hanging on an insert into a freshly created table on an installation thats only existed for 30 minutes and only just had all the tables created. Thanks Shane
You should upgrade to the latest version (7.1.3) and see if you're still experiencing the same problems..I'm sure you're interested in finding out why it's happening but upgrading is still a good idea.... I'm almost positive that the RPMs are available for 7.1.3.. -Mitch ----- Original Message ----- From: "Shane Wright" <me@shanewright.co.uk> To: <pgsql-general@postgresql.org> Sent: Saturday, September 22, 2001 1:58 PM Subject: [GENERAL] backend stalls > Hi > > I'm tearing my hair out here, the backend seems to randomly decide to stall > and not serve any more queries (processes are listed as waiting). > > It happens on all sorts of queries (including CREATE TABLE and CREATE INDEX). > > I have completely uninstalled and deleted the whole installation and > reinstalled - only to have it do it again mid way through entering the SQL to > rebuild my database (not a big one ~25 tables, and no rows to speak of - > havent got that far yet). > > I was thinking corrupted tables - or corrupt system catalog, but even > vacuumdb stalls as well... > > Any help would be appreciated, I have so much work to do and I cant do > anything without the database working :( > > My install is Postgres 7.0.3-8 from the RedHat RPMs runing on RH7.1 > > I know I havent given much specific information, I dont really know where to > start. What its doing at this very minute is hanging on an insert into a > freshly created table on an installation thats only existed for 30 minutes > and only just had all the tables created. > > Thanks > > Shane > > ---------------------------(end of broadcast)--------------------------- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org) >
Any chance you're running out of disk space somewhere? Have you looked in the log file for clues? (/var/log/postgres.log on debian - not sure if the location is the same on other OSs.) -Nick --------------------------------------------------------------------- Nick Fankhauser Business: nickf@doxpop.com Phone 1.765.965.7363 Fax 1.765.962.9788 doxpop - Court records at your fingertips - http://www.doxpop.com/ Personal: nick@fankhausers.com http://www.fankhausers.com > -----Original Message----- > From: pgsql-general-owner@postgresql.org > [mailto:pgsql-general-owner@postgresql.org]On Behalf Of Shane Wright > Sent: Saturday, September 22, 2001 12:59 PM > To: pgsql-general@postgresql.org > Subject: [GENERAL] backend stalls > > > Hi > > I'm tearing my hair out here, the backend seems to randomly > decide to stall > and not serve any more queries (processes are listed as waiting). > > It happens on all sorts of queries (including CREATE TABLE and > CREATE INDEX). > > I have completely uninstalled and deleted the whole installation and > reinstalled - only to have it do it again mid way through > entering the SQL to > rebuild my database (not a big one ~25 tables, and no rows to speak of - > havent got that far yet). > > I was thinking corrupted tables - or corrupt system catalog, but even > vacuumdb stalls as well... > > Any help would be appreciated, I have so much work to do and I cant do > anything without the database working :( > > My install is Postgres 7.0.3-8 from the RedHat RPMs runing on RH7.1 > > I know I havent given much specific information, I dont really > know where to > start. What its doing at this very minute is hanging on an insert into a > freshly created table on an installation thats only existed for > 30 minutes > and only just had all the tables created. > > Thanks > > Shane > > ---------------------------(end of broadcast)--------------------------- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org) >
Mitch We've just ordered a new server from our hosting providers and requested that it have the latest version on it so we will be upgrading. I havent been able to find RPMS for RedHat for 7.1.3 though - although RedHat are always a way behind... Thanks Shane On Thursday 27 September 2001 8:26 pm, you wrote: > You should upgrade to the latest version (7.1.3) and see if you're still > experiencing the same problems..I'm sure you're interested in finding out > why it's happening but upgrading is still a good idea.... I'm almost > positive that the RPMs are available for 7.1.3.. > > > -Mitch > > ----- Original Message ----- > From: "Shane Wright" <me@shanewright.co.uk> > To: <pgsql-general@postgresql.org> > Sent: Saturday, September 22, 2001 1:58 PM > Subject: [GENERAL] backend stalls > > > Hi > > > > I'm tearing my hair out here, the backend seems to randomly decide to > > stall > > > and not serve any more queries (processes are listed as waiting). > > > > It happens on all sorts of queries (including CREATE TABLE and CREATE > > INDEX). > > > I have completely uninstalled and deleted the whole installation and > > reinstalled - only to have it do it again mid way through entering the > > SQL > > to > > > rebuild my database (not a big one ~25 tables, and no rows to speak of - > > havent got that far yet). > > > > I was thinking corrupted tables - or corrupt system catalog, but even > > vacuumdb stalls as well... > > > > Any help would be appreciated, I have so much work to do and I cant do > > anything without the database working :( > > > > My install is Postgres 7.0.3-8 from the RedHat RPMs runing on RH7.1 > > > > I know I havent given much specific information, I dont really know where > > to > > > start. What its doing at this very minute is hanging on an insert into a > > freshly created table on an installation thats only existed for 30 > > minutes and only just had all the tables created. > > > > Thanks > > > > Shane > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 2: you can get off all lists at once with the unregister command > > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org) -- Shane Wright eMysteryShopper.com 2 Berrywood Business Village Hedge End Southampton Hampshire SO30 2UN Tel: +44 (0) 1489 772933 Fax: +44 (0) 1489 772922 This message is sent in confidence for the addressee only. The contents are not to be disclosed to anyone other than the addressee. Unauthorised recipients must preserve this confidentiality and should please advise the sender immediately of any error in transmission. Any attachment(s) to this message has been checked for viruses, but please rely on your own virus checker and procedures.
Hi > Any chance you're running out of disk space somewhere? Loads of free space :) > Have you looked in the log file for clues? I tried- but I cant find a log that looks vaguely to do with postgres that isnt binary data (?). Interestingly, I tried setting up on a different machine and the same things happened (same OS, same pg version) - but back on the original machine if I symlink /var/lib/pgsql to point to a directory on another disk it all seems to be ok. I'm perhaps thinking it may be some conflict between pg and the system somehow (?) Shane > > -----Original Message----- > > From: pgsql-general-owner@postgresql.org > > [mailto:pgsql-general-owner@postgresql.org]On Behalf Of Shane Wright > > Sent: Saturday, September 22, 2001 12:59 PM > > To: pgsql-general@postgresql.org > > Subject: [GENERAL] backend stalls > > > > > > Hi > > > > I'm tearing my hair out here, the backend seems to randomly > > decide to stall > > and not serve any more queries (processes are listed as waiting). > > > > It happens on all sorts of queries (including CREATE TABLE and > > CREATE INDEX). > > > > I have completely uninstalled and deleted the whole installation and > > reinstalled - only to have it do it again mid way through > > entering the SQL to > > rebuild my database (not a big one ~25 tables, and no rows to speak of - > > havent got that far yet). > > > > I was thinking corrupted tables - or corrupt system catalog, but even > > vacuumdb stalls as well... > > > > Any help would be appreciated, I have so much work to do and I cant do > > anything without the database working :( > > > > My install is Postgres 7.0.3-8 from the RedHat RPMs runing on RH7.1 > > > > I know I havent given much specific information, I dont really > > know where to > > start. What its doing at this very minute is hanging on an insert into a > > freshly created table on an installation thats only existed for > > 30 minutes > > and only just had all the tables created. > > > > Thanks > > > > Shane > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 2: you can get off all lists at once with the unregister command > > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org) -- Shane Wright eMysteryShopper.com 2 Berrywood Business Village Hedge End Southampton Hampshire SO30 2UN Tel: +44 (0) 1489 772933 Fax: +44 (0) 1489 772922 This message is sent in confidence for the addressee only. The contents are not to be disclosed to anyone other than the addressee. Unauthorised recipients must preserve this confidentiality and should please advise the sender immediately of any error in transmission. Any attachment(s) to this message has been checked for viruses, but please rely on your own virus checker and procedures.