Re: initdb failure (was Re: [GENERAL] sequence's plpgsql) - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)
Date
Msg-id 20030927172145.GA2290@dcc.uchile.cl
Whole thread Raw
In response to Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
On Sat, Sep 27, 2003 at 01:08:37PM -0400, Bruce Momjian wrote:
> Peter Eisentraut wrote:

> > That is all besides the point.  If adding -f to the command line is for
> > some reason prohibitive, then the same applies to -e.  That is all.
> 
> Seems we should recommend -f rather than "<" for restores anyway, right?

Please keep in mind that it is not always possible to use -f.  In my
case I had a file larger than 2GB and psql was compiled without large
file support.  Detecting an error in that situation would have required
recompiling psql.

Also I don't see the point in not extending the context message of the
error.  It's not like it's going to take too much processing power, nor
screen estate, so what is it?

-- 
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"Right now the sectors on the hard disk run clockwise, but I heard a rumor that
you can squeeze 0.2% more throughput by running them counterclockwise.
It's worth the effort. Recommended."  (Gerry Pourwelle)


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)
Next
From: Tom Lane
Date:
Subject: Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)