Re: pg_dump and transactions - Mailing list pgsql-patches

From Ferdinand Smit
Subject Re: pg_dump and transactions
Date
Msg-id 200203211553.g2LFrZH09812@server9.telegraafnet.nl
Whole thread Raw
In response to Re: pg_dump and transactions  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: pg_dump and transactions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
Hi Bruce,

> Can you explain the COPY troubles you have had.  Seems like a problem.

We have about 30 different postgres databases and de versions differ from 6.5
to 7.3. Maybe that causes sometimes the poblem.
An other thing is dat COPY fails when you use "strange characters". Expecialy
when you are changing from encoding. (Lots of trouble with changing from
unicode to sql-ascii)

> What about this patch which batches INSERTS into transaction blocks?
> Seems if you are worried about performance, you should be using COPY.  I
> am not inclined to apply it but rather find out why COPY isn't working
> for this person.

Wy not ?? I think that transactions in a dump are a normal thing. Beside of
that, our database-dumps must be useble even when we change from version or
database-type.

Ferdinand

pgsql-patches by date:

Previous
From: Fernando Nasser
Date:
Subject: Re: Domain Support -- another round
Next
From: Thomas Lockhart
Date:
Subject: Re: Domain Support -- another round