X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id CB4BC9FB6AC for ; Fri, 1 Sep 2006 16:21:39 -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 20287-04-5 for ; Fri, 1 Sep 2006 16:21:00 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id DA95E9FB76B for ; Fri, 1 Sep 2006 13:42:55 -0300 (ADT) Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com ([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ; Fri, 1 Sep 2006 16:42:50 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 01 Sep 2006 11:42:50 -0500 Subject: Re: problem with initlocation From: Scott Marlowe To: "Josef J. Micka" Cc: pgsql-admin@postgresql.org In-Reply-To: <44F84E51.7090201@maylo.cz> References: <44F84E51.7090201@maylo.cz> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1157128970.4786.2.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Fri, 01 Sep 2006 11:42:50 -0500 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.085 tagged_above=0 required=5 tests=AWL, SPF_PASS, UNPARSEABLE_RELAY X-Spam-Level: X-Archive-Number: 200609/10 X-Sequence-Number: 22924 On Fri, 2006-09-01 at 10:14, Josef J. Micka wrote: > Joshua D. Drake wrote: > > > Scott Marlowe wrote: > >> > >> What does the command whoami say right before you would run the > >> initlocation? > > > > > > > > I think a more appropriate question would be why is he running a > > version of PostgreSQL that still has initlocation? > > > because it's latest stable version for debian sarge. > and i rather use possibly "older but stable" software, then "unstable" > or "development" software on production server. > also i don't need features of new version, in fact, i may stay on 6.5, > but from my point of view is 7.4 faster, and as i said, it's "stable" > for debian. As someone else who is running 7.4, I can say that while I'd love to push 8.0 or 8.1 into production, it often takes a year or more from the time something is released until it can be used. But I don't think I'd run any version of PostgreSQL older than 7.3 in production. There were major, data losing bugs in versions before that version that make them unsuitable for production, like transaction ID wrap around.