X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 7FB389FA4F2 for ; Fri, 5 May 2006 04:48:28 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 82798-01 for ; Fri, 5 May 2006 04:48:22 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from bigmail.jlaltd.co.uk (bigmail.jla.com [81.171.198.99]) by postgresql.org (Postfix) with ESMTP id DB8389FA294 for ; Fri, 5 May 2006 04:48:21 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by bigmail.jlaltd.co.uk (Postfix) with ESMTP id 6680B2A9994; Fri, 5 May 2006 08:46:07 +0000 (GMT) Received: from bigmail.jlaltd.co.uk ([127.0.0.1]) by localhost (bigmail [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24499-08; Fri, 5 May 2006 08:46:04 +0000 (GMT) Received: from [192.168.0.228] (unknown [192.168.0.228]) by bigmail.jlaltd.co.uk (Postfix) with ESMTP id E7DAC2A994A; Fri, 5 May 2006 08:46:04 +0000 (GMT) Message-ID: <445B1110.506@jla.com> Date: Fri, 05 May 2006 08:47:12 +0000 From: Steve Burrows User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 Cc: Shivaji S , pgsql-admin@postgresql.org Subject: Re: How to find current running process References: <20060504202117.32050.qmail@webmail46.rediffmail.com> <4493.1146775691@sss.pgh.pa.us> In-Reply-To: <4493.1146775691@sss.pgh.pa.us> Content-Type: multipart/alternative; boundary="------------030207010905020504020304" X-Virus-Scanned: by amavisd-new at jla.com X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/53 X-Sequence-Number: 21585 This is a multi-part message in MIME format. --------------030207010905020504020304 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Got to echo this sentiment. I started using Postgresql commercially with version 6.5. I used Postgresql 7.1 from its release until earlier this year when it ate my data warehouse! Didn't upgrade because the solution was stable for several years then the whole thing blew up with the wraparound problem. I had to work very hard and was very lucky to recover it all. Please upgrade ASAP, it will be unpleasant, you may have to adjust code in some applications because of syntax changes etc., but that's a lot cheaper than losing your data. Steve Tom Lane wrote: > "Shivaji S" writes: > >> tom thanks for the input ,but the below queries doesn't support for my post= >> gres version 7.1.1 >> > > 7.1.1? Egad. Update to something remotely modern, before it eats > your data. The list of bugs fixed since then would curl your toes. > See for yourself: > http://developer.postgresql.org/docs/postgres/release.html > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Have you searched our list archives? > > http://archives.postgresql.org > --------------030207010905020504020304 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Got to echo this sentiment. I started using Postgresql commercially with version 6.5.  I used Postgresql 7.1 from its release until earlier this year when it ate my data warehouse! Didn't upgrade because the solution was stable for several years then the whole thing blew up with the wraparound problem. I had to work very hard and was very lucky to recover it all. Please upgrade ASAP, it will be unpleasant, you may have to adjust code in some applications because of syntax changes etc., but that's a lot cheaper than losing your data.

Steve

Tom Lane wrote:
"Shivaji S" <s.shivaji@rediffmail.com> writes:
  
tom thanks for the input ,but the below queries doesn't support for my post=
gres version 7.1.1
    

7.1.1?  Egad.  Update to something remotely modern, before it eats
your data.  The list of bugs fixed since then would curl your toes.
See for yourself:
http://developer.postgresql.org/docs/postgres/release.html

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

               http://archives.postgresql.org
  

--------------030207010905020504020304--