Re: restore whoes

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Simone Tellini <tellini(at)areabusiness(dot)it>, pgsql-admin(at)postgresql(dot)org
Subject: Re: restore whoes
Date: 2002-02-11 21:07:11
Message-ID: 200202112107.g1BL7Bl19886@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > I just think forcing the escape of \r isn't reasonable.
>
> It's not ideal, certainly, but I think it's preferable to continuing
> to get burned every time a pg_dump file comes within hailing distance
> of Windoze. We've seen these complaints over and over, and we'll
> continue to see them again and again until we do something to become
> proof against the problem. There is no solution that doesn't involve
> some amount of backwards-incompatibility. So let's bite the bullet and
> do it. We can offer a GUC switch to provide the old COPY IN behavior
> for people who need it --- but given the shape of the world today, the
> default behavior needs to be Microsoft-proof.

I am afraid we will fix the \r\n problem but cause many more problems
with old dumps and hand-created COPY files.

What if we add GUC param and keep the behavior unchanged?

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2002-02-11 21:27:12 Re: restore whoes
Previous Message Tom Lane 2002-02-11 20:42:29 Re: restore whoes