Re: initdb in current cvs head broken?

From: Sushant Sinha <sushant354(at)gmail(dot)com>
To: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
Cc: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: initdb in current cvs head broken?
Date: 2008-07-10 12:52:43
Message-ID: 1215694363.5948.26.camel@dragflick
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

You are right. I did not do make clean last time. After make clean, make
all, and make install it works fine.

-Sushant.

On Thu, 2008-07-10 at 17:55 +0530, Pavan Deolasee wrote:
> On Thu, Jul 10, 2008 at 5:36 PM, Sushant Sinha <sushant354(at)gmail(dot)com> wrote:
> >
> >
> >
> > Seems like a bug to me. Is the tree stable only after commit fests and I
> > should not use the unstable tree for generating patches?
> >
>
> I quickly tried on my repo and its working fine. (Well it could be a
> bit out of sync with the head).
>
> Usually, the tree may get a bit inconsistent during the active period,
> but its not very common. I've seen committers doing a good job before
> checking in any code and making sure it works fine (atleast initdb and
> regression tests).
>
> I would suggest doing a clean build at your end once again.
>
> Thanks,
> Pavan
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2008-07-10 12:56:13 Re: CREATE CAST too strict?
Previous Message Andrew Dunstan 2008-07-10 12:47:48 Re: initdb in current cvs head broken?