From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Simone Tellini <tellini(at)areabusiness(dot)it> |
Cc: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: restore whoes |
Date: | 2002-02-11 18:35:39 |
Message-ID: | 20020211103050.D81764-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Mon, 11 Feb 2002, Simone Tellini wrote:
>
> On Mon, 11 Feb 2002 11:56:28 -0500
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> TL> > err... probably I didn't make it clear, but the problem is that you
> TL> > can't restore a database if you've got a text field containing CRLF
> TL> > terminated text!
> TL> Au contraire: it works fine ... so long as the COPY data hasn't been
> TL> munged between being emitted and being reloaded.
>
> no, it doesn't.
>
> I'll repeat myself: I've dumped the database on 7.1.3 and tried to
> restore it with 7.2 on the same Linux machine without modifying the dump.
> It didn't work at all.
I just did a test on a debian machine from 7.1.3 to 7.2 with CRLF included
text with no apparent problems. There must be something more to it that
that.
create table a(a text);
insert into a values ('abc\015\012abc');
insert into a values ('abc\015\012');
insert into a values ('\015\012');
insert into a values ('\015\012abc');
insert into a values ('\015\012');
insert into a values ('\015');
insert into a values ('abc\015');
- dump and restore then worked properly for the database containing this
table including restoring the CRs and LFs afaics
From | Date | Subject | |
---|---|---|---|
Next Message | Chad R. Larson | 2002-02-11 18:38:53 | Re: Restore Question |
Previous Message | James Kelty | 2002-02-11 18:24:04 | Replication...??? |