Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id A177C9FBABC for ; Mon, 25 Jun 2007 16:28:25 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 24394-01 for ; Mon, 25 Jun 2007 16:28:22 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by postgresql.org (Postfix) with ESMTP id 35DFE9FBAAC for ; Mon, 25 Jun 2007 16:28:25 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.8/8.13.8) with ESMTP id l5PJSL3R044024 for ; Mon, 25 Jun 2007 16:28:21 -0300 (ADT) (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.8/8.13.8/Submit) id l5PJ434Q039123 for pgsql-admin@postgresql.org; Mon, 25 Jun 2007 16:04:03 -0300 (ADT) (envelope-from news) From: Chris Browne X-Newsgroups: pgsql.admin Subject: Re: database creation date Date: Mon, 25 Jun 2007 14:40:44 -0400 Organization: cbbrowne Computing Inc Lines: 43 Message-ID: <60fy4f3mj7.fsf@dba2.int.libertyrms.com> References: <3aa3ccbb0706250955s3422d425o72ffcce43342a308@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@news.hub.org User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.20 (linux) Cancel-Lock: sha1:U+jQoE+t//W1prwG3E8aFEUyJm4= To: pgsql-admin@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/266 X-Sequence-Number: 25934 chandru.dba@gmail.com ("Pradeep Chandru") writes: > Hi, >   I have two questions. > 1. Is there a way to find the database creation time? Elderly timestamps on files in the database's directory would be an approximation to that. > 2. Is WAL implementation possible in postgres7.1.1? If so > simple steps for the same? This is required to migrate from > the older setup to the latest version in parallel without > disturbing the current setup. There isn't a reasonable way, as far as I know, to 'replicate' from PostgreSQL 7.1 to anything newer. You would need to: 1. shut down all apps accessing the database, 2. do a pg_dump to extract current data, 3. load that into a newer version of PostgreSQL, 4. verify that all looks good, and 5. point the apps to the new database on the new version. If the database is fairly large, the time between steps 1 and 5 could be fairly substantial. If you were on a newer version of PostgreSQL, say 7.3, you might be able to use something like Slony-I to replicate data into a newer version; that could make the outage time pretty short. But PostgreSQL 7.1.1 is *very* old. -- (reverse (concatenate 'string "ofni.secnanifxunil" "@" "enworbbc")) http://cbbrowne.com/info/slony.html "... the open research model is justified. There is a passage in the Bible (John 8:32, and on a plaque in CIA HQ), "And ye shall know the truth, and the truth shall set ye free." -- Dave Dittrich