Re: [HACKERS] initdb failure (was Re: [GENERAL] sequence's plpgsql)

2003-09-26 Thread Bruce Momjian
Peter Eisentraut wrote: Tom Lane writes: so it appears that cygwin's echo generates a different newline style than what got put into sql_features.txt. A possible way to fix this is to put the \. line into sql_features.txt, but maybe there's a cleaner answer. Peter, any thoughts?

Re: [HACKERS] initdb failure (was Re: [GENERAL] sequence's plpgsql)

2003-09-26 Thread Jon Jensen
On Fri, 26 Sep 2003, Tom Lane wrote: I was chewing this over with Bruce on the phone just now, and we refined the idea a little. Some errors (primarily those detected inside the datatype input procedures) can be clearly traced to a specific column, whereas others (such as too many fields on

Re: [HACKERS] initdb failure (was Re: [GENERAL] sequence's plpgsql)

2003-09-26 Thread Bruce Momjian
Jon Jensen wrote: On Fri, 26 Sep 2003, Tom Lane wrote: I was chewing this over with Bruce on the phone just now, and we refined the idea a little. Some errors (primarily those detected inside the datatype input procedures) can be clearly traced to a specific column, whereas others

Re: [HACKERS] initdb failure (was Re: [GENERAL] sequence's plpgsql)

2003-09-26 Thread Oliver Elphick
On Fri, 2003-09-26 at 23:18, Bruce Momjian wrote: If you are loading from pg_dump, you have lots of copy commands, so how do you know which COPY command caused the failure. You just have the line number of _a_ copy. I would recommend using psql -e so that the sql commands are output too.

Re: [HACKERS] InitDB Failure - PostgreSQL 7.2, RedHat 7.3, compile from source

2002-11-28 Thread Tom Lane
[EMAIL PROTECTED] writes: Due to the 32 character limit on column/table names, we needed to recompile PostgreSQL from the source with updated settings. It compiles fine, but on running initdb, we get the following output: Without bothering to examine the details, I'll bet you didn't do a full

[HACKERS] InitDB Failure - PostgreSQL 7.2, RedHat 7.3, compile from source

2002-11-27 Thread chris
Hi, Sorry to ask this question straight out but I wasn't sure where else to get an answer! Due to the 32 character limit on column/table names, we needed to recompile PostgreSQL from the source with updated settings. It compiles fine, but on running initdb, we get the following output:

Re: [HACKERS] initdb failure

2000-11-09 Thread Tom Lane
"Kevin O'Gorman" [EMAIL PROTECTED] writes: I'm just catching up to the tip of the current tree, and find that I have a reported failure in initdb. initdb works fine for me (as of CVS from about 11:30AM EST today). Try running it with -d or -v or whatever the verbose-output option is to get

<    1   2