Re: COPY Hacks (WAS: RE: Postgresql vs SQLserver for this application ?)

Поиск
Список
Период
Сортировка
От Harald Fuchs
Тема Re: COPY Hacks (WAS: RE: Postgresql vs SQLserver for this application ?)
Дата
Msg-id puwtreg4ke.fsf@srv.protecting.net
обсуждение исходный текст
Ответ на RE : RE: Postgresql vs SQLserver for this application ?  (bsimon@loxane.com)
Список pgsql-performance
In article <1112813199.42542e8f17b4d@webmail.telus.net>,
Mischa <mischa.Sandberg@telus.net> writes:

> This thread seems to be focusing in on COPY efficiency,
> I'd like to ask something I got no answer to, a few months ago.

> Using COPY ... FROM STDIN via the Perl DBI (DBD::Pg) interface,
> I accidentally strung together several \n-terminated input lines,
> and sent them to the server with a single "putline".

> To my (happy) surprise, I ended up with exactly that number of rows
> in the target table.

> Is this a bug? Is this fundamental to the protocol?

> Since it hasn't been documented (but then, "endcopy" isn't documented),
> I've been shy of investing in perf testing such mass copy calls.
> But, if it DOES work, it should be reducing the number of network
> roundtrips.

> So. Is it a feechur? Worth stress-testing? Could be VERY cool.

Using COPY from DBD::Pg _is_ documented - presumed you use DBD::Pg
version 1.41 released just today.

В списке pgsql-performance по дате отправления:

Предыдущее
От: "Douglas J. Trainor"
Дата:
Сообщение: Re: How to improve db performance with $7K?
Следующее
От: Bruno Wolff III
Дата:
Сообщение: Re: Recognizing range constraints (was Re: Plan for relatively simple query seems to be very inefficient)