Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g11Kegl41109 for ; Fri, 1 Feb 2002 15:40:43 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g11Kdqf12672; Fri, 1 Feb 2002 15:39:52 -0500 (EST) To: "David M. Richter" cc: pgsql-sql@postgresql.org Subject: Re: pg_vlock / vacuum In-reply-to: <3C5AA7D4.5E63CA2B@dkfz.de> References: <3C5AA7D4.5E63CA2B@dkfz.de> Comments: In-reply-to "David M. Richter" message dated "Fri, 01 Feb 2002 15:36:04 +0100" Date: Fri, 01 Feb 2002 15:39:52 -0500 Message-ID: <12669.1012595992@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200202/28 X-Sequence-Number: 6460 "David M. Richter" writes: > We are using Suse Linux 7.3 with postgres 6.5.3. 6.5.3? Run, do not walk, to your nearest FTP server and get an update. > I cannot see a file named pg_vlock in that directory! Possibly restarting the postmaster would get you out of trouble. However, the list of bugs fixed since 6.5.* is longer than you really want to know about. Please update ASAP. regards, tom lane