| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martin Gregorie <martin(at)gregorie(dot)org> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Problem with the pg_dumpall file format |
| Date: | 2008-10-19 14:41:34 |
| Message-ID: | 10721.1224427294@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Martin Gregorie <martin(at)gregorie(dot)org> writes:
> For some reason, when my message table (see below) is dumped, blank
> lines are introduced between rows.
Nothing like that has been reported before. We have heard of dump files
getting corrupted after they've been produced --- the most common case
is newlines (\n) getting converted to carriage-return-line-feed (\r\n)
due to being copied onto a Windows machine. The COPY data format is
reasonably impervious to that, but I suppose it's possible that a second
conversion step might incorrectly change \r\n to \n\n.
If you're certain that nothing is happening to the dump file after the
fact, then we'll need to see a self-contained test case.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2008-10-20 08:40:21 | Re: BUG #4455: Valid SSL certificate reported as expired |
| Previous Message | hubert depesz lubaczewski | 2008-10-19 01:01:09 | ftp server symlink |