Re: pg_dump and transactions

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Ferdinand Smit <ferdinand(at)telegraafnet(dot)nl>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: pg_dump and transactions
Date: 2002-03-21 14:43:20
Message-ID: 200203211443.g2LEhKF17911@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches


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

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.

---------------------------------------------------------------------------

Ferdinand Smit wrote:
> Hi,
>
> We have lots of trouble with using the COPY dump, so we always use de INSERT
> mode. Because the INSERT mode does'nt use transactions, this methode is very
> slow.
>
> This (simple) patch creates (if the -T flag is set) a transaction of every
> insert block, so de import is mostly 10 times faster.
>
> I hope you like it.
> Regards,
>
> Ferdinand

[ Attachment, skipping... ]

>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Rod Taylor 2002-03-21 15:03:20 Re: Domain Support -- another round
Previous Message Ferdinand Smit 2002-03-21 10:33:34 pg_dump and transactions