Re: pg_dump and transactions

Hi,

> >> Can you explain the COPY troubles you have had.  Seems like a problem.
>
> This is completely unhelpful.  Give us a specific case that fails in
> the current release, and we can try to fix it.  No, we do not want to
> hear about how you're afraid of COPY because it had bugs in 6.5.
>

Sorry i was in a hurry.

The export-database is PG 7.0.3 in UNICODE.
The export-table is from type text.
The import-database is PG 7.3 in SQL-ASCII.

The problem-records has an euro-sign.

teleportal=# \d uiting
                             Table "uiting"
 Attribute |   Type    |                    Modifier
-----------+-----------+-------------------------------------------------
 id        | integer   | not null default nextval('uiting_id_seq'::text)
 carrousel | integer   | not null
 tekst     | text      |
 url       | text      | not null
 start     | timestamp |
 einde     | timestamp |
 clicks    | integer   | not null default 0
 views     | integer   | default 0
 otherid   | integer   |
 inarchief | boolean   |
Index: uiting_pkey

teleportal=# select tekst from uiting where id = 26109;
                           tekst
-----------------------------------------------------------
Audi TT Coupé 2000, 77.000km € 33.850
(1 row)
teleportal=#

The COPY dump gives :
26109   4       Audi TT Coupé 2000, 77.000km~@| 33.850
http://autotelegraaf.nl/GebruiktOpWeg/Speurder/Toon/?id=475739&referrer=etalage
\N      2002-03-26 14:12:00+01  1907    630563  475739  t

The INSERT dump gives:
INSERT INTO "uiting" VALUES (26109,4,'Audi TT Coup\351 2000, 77.000km
\200\24033.850','http://autotelegraaf.nl/GebruiktOpWeg/Speurder/Toon/?id=475739&referrer=etalage',NULL,'2002-03-26
14:12:00+01',1907,630563,475739,'t');

Regards,
Ferdinand