From: | Euler Taveira de Oliveira <eulerto(at)yahoo(dot)com(dot)br> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Luiz K(dot) Matsumura" <luiz(at)planit(dot)com(dot)br> |
Cc: | pgsql-patches(at)postgresql(dot)org |
Subject: | Re: problem with CR+LF in files in psql \i command |
Date: | 2005-03-26 11:32:25 |
Message-ID: | 20050326113225.17283.qmail@web54606.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Hi Bruce,
> Function and comments are just _strings_ to PostgreSQL, so we have no
> good way of cleaning the output up, unless we hack pg_dump to somehow
> change line endings when outputting such information, though
> currently we
> don't. The would perhaps cause problems in viewing the functions if
> restored in Win32.
>
Agreed.
> Fixing it at the \i level is too crude because it might remove
> carriage
> returns that are wanted in the input stream.
>
Agreed.
> We are open to ideas on how to improve this.
>
What about another option to pg_dump to indicate such a thing? Maybe -l
or --change-line [m|w|u]
Another TODO item?
Euler Taveira de Oliveira
euler[at]yahoo_com_br
__________________________________________________
Converse com seus amigos em tempo real com o Yahoo! Messenger
http://br.download.yahoo.com/messenger/
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2005-03-26 14:47:57 | Re: minor windows & cygwin regression failures on stable |
Previous Message | Oleg Bartunov | 2005-03-26 10:41:38 | understanding pg_stat* numbers |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-03-26 17:59:48 | Re: [PATCHES] problem with CR+LF in files in psql \i command |
Previous Message | Bruce Momjian | 2005-03-26 02:44:52 | Re: problem with CR+LF in files in psql \i command |