Re: Postgre SQL 7.1 cygwin performance issue.

On 8/28/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Christopher Browne" <cbbrowne(at)gmail(dot)com> writes:
> > On 8/28/06, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> >> There's no solution short of upgrading.
>
> > That's a little too negative. There is at least one alternative,
> > possibly two...
>
> But both of those would probably involve work comparable to an upgrade.

We don't know what is preventing the upgrade; we haven't been told
anything about the details surrounding that.

> There is another reason for not encouraging these folk to stay on 7.1
> indefinitely, which is that 7.1 still has the transaction ID wraparound
> problem. It *will* --- not might, WILL --- eat their data someday.
> Without knowing anything about their transaction rate, I can't say
> whether that will happen tomorrow or not for many years, but insisting
> on staying on 7.1 is a dangerous game.

Fair enough. I would only suggest these workarounds as a way of
getting a bit of temporary "breathing room" before doing the upgrade.

These should at best be considered temporary workarounds, because
there are around 50 releases that have been made since 7.1.3. All but
a handful of those releases (namely 7.2.0, 7.3.0, 7.4.0, 8.0.0, and
8.1.0) were created because of discovering "eat your data" problems of
one variety or another.
--
http://www3.sympatico.ca/cbbrowne/linux.html
Oddly enough, this is completely standard behaviour for shells. This
is a roundabout way of saying `don't use combined chains of `&&'s and
`||'s unless you think Gödel's theorem is for sissies'.