From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
---|---|
To: | "Josef J(dot) Micka" <postgres(at)maylo(dot)cz> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: problem with initlocation |
Date: | 2006-09-01 16:42:50 |
Message-ID: | 1157128970.4786.2.camel@state.g2switchworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2006-09-01 17:47:13 | Re: problem with initlocation |
Previous Message | Tom Lane | 2006-09-01 16:02:04 | Re: Problem using pg_restore with -a option |