Re: Initdb failed in PostgreSQL 7.3.21

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
Cc: "Kakoli Sen" <kakolis(at)cdacb(dot)ernet(dot)in>, pgsql-general(at)postgresql(dot)org
Subject: Re: Initdb failed in PostgreSQL 7.3.21
Date: 2008-02-18 21:11:20
Message-ID: 1221.1203369080@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> writes:
> On Feb 18, 2008 1:44 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Why are you intent on making a fresh installation of 7.3.x anyway?
>> Seems like it'd be better to take the opportunity to move to a
>> non-obsolete release.

> Who knows? He might have a 6.5.3 server somewhere huffing away and
> he's busy installing various versions as halfway points. Just a
> guess. I had the same reaction as you. I certainly hope it's not
> being setup for new development, but sometimes I have to blow the dust
> off an old server and run old software.

Sure, he might have a good reason for it. I was just thinking that
if he'd picked that version for no particularly strong reason, it'd
likely be easier to debug this problem (if it even still exists) using
a more modern release branch. Blowing dust off our recollections about
7.3 is not such an easy thing.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2008-02-18 21:35:11 Re: Pains in upgrading to 8.3
Previous Message Tom Lane 2008-02-18 20:58:52 Re: deadlock with truncate and foreing keys