| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | tach(at)valinux(dot)co(dot)jp |
| Cc: | "PostgreSQL Bugs List" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #1050: cannot restore db at postgresql 7.4.1 |
| Date: | 2004-01-15 04:49:54 |
| Message-ID: | 19567.1074142194@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"PostgreSQL Bugs List" <pgsql-bugs(at)postgresql(dot)org> writes:
> The release notes of 7.4 saids:
> COPY now can process files that use carriage-return or
> carriage-return/line-feed end-of-line sequences. Literal carriage-returns
> and line-feeds are no longer accepted in data values; use \r and \n instead.
> I think this is bug and pg_dump/pg_restore should
> be fixed to keep with this modification.
This was a deliberate change and will not be undone, even though it does
create compatibility issues with dumps from very old PG versions.
The best workaround I know of for dumping from such an old server is to
use the "dump as INSERT commands" option.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2004-01-15 10:37:03 | Re: jdbc1.AbstractJdbc1Statement.setBinaryStream bug and |
| Previous Message | PostgreSQL Bugs List | 2004-01-15 04:29:46 | BUG #1050: cannot restore db at postgresql 7.4.1 |