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

From Tom Lane
Subject Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)
Date
Msg-id 6474.1064683586@sss.pgh.pa.us
Whole thread Raw
In response to Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Peter Eisentraut wrote:
>> Maybe instead we can change the COPY command to read the file directly and
>> not via stdin?  Then we don't need the \. marker.

I like that idea too.

> Yes, we need a temp table then.  The single-line fix seemed easier.

Why a temp table?  The COPY command is only sourcing the contents of
"$datadir"/sql_features.txt.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
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)