Re: Re: Unknown Type 'ame' [urgent] - Mailing list pgsql-general

From Tom Lane
Subject Re: Re: Unknown Type 'ame' [urgent]
Date
Msg-id 14813.979687736@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: Unknown Type 'ame' [urgent]  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Re: Unknown Type 'ame' [urgent]  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-general
Bruce Momjian <pgman@candle.pha.pa.us> writes:
>> -e "s/[    ]NameData/\ name/g" \
>> -e "s/^NameData/\name/g" \

> What is that \n doing in there?  It is certainly wrong.  I am just
> wondering what is should be.

It's been like that since 1996, according to the CVS logs.  I'm
surprised we have not had more reports of trouble --- either the shell
or sed might be deciding to translate that \n to a newline, although
evidently the consensus behavior is not to.

I zapped the gratuitous backslashes before the spaces, too, just
for luck.

            regards, tom lane

pgsql-general by date:

Previous
From: "Craig L. Ching"
Date:
Subject: RE: Why is there so much MySQL bashing???
Next
From: "Abe"
Date:
Subject: Postgres Warning - index 1