Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id EE0CF475EE2 for ; Fri, 24 Jan 2003 16:27:56 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 20339476027 for ; Fri, 24 Jan 2003 16:01:42 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h0OL1f5u022651; Fri, 24 Jan 2003 16:01:42 -0500 (EST) To: Carlos Moreno Cc: PgSQL Performance ML Subject: Re: Having trouble with backups (was: Re: Crash Recovery) In-reply-to: <3E3158DA.7080807@mochima.com> References: <2147483647.1043361178@[10.0.1.133]> <1043416377.29437.70.camel@haggis> <3E3158DA.7080807@mochima.com> Comments: In-reply-to Carlos Moreno message dated "Fri, 24 Jan 2003 10:16:42 -0500" Date: Fri, 24 Jan 2003 16:01:41 -0500 Message-ID: <22650.1043442101@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/292 X-Sequence-Number: 939 Carlos Moreno writes: > And the second (and intriguing) problem: whenever I run pg_dump, > my system *freezes* until pg_dump finishes. When I say "system", > I mean the software that is running and sending data to the PG > database. Other people have responded on the assumption that this is a performance problem, but you should also consider the possibility that it's bad coding of your application software. Does your app try to grab exclusive table locks? If so, it'll sit there waiting for the pg_dump to complete. pg_dump only takes ACCESS SHARE lock on the tables it's working on, which is the weakest type of lock and does not conflict with most database operations ... but it does conflict with ACCESS EXCLUSIVE lock requests. regards, tom lane