Re: COPY and Volatile default expressions
От | David Fetter |
---|---|
Тема | Re: COPY and Volatile default expressions |
Дата | |
Msg-id | 20130415160804.GL5337@fetter.org обсуждение исходный текст |
Ответ на | Re: COPY and Volatile default expressions (Simon Riggs <simon@2ndQuadrant.com>) |
Ответы |
Re: COPY and Volatile default expressions
Re: COPY and Volatile default expressions |
Список | pgsql-hackers |
On Mon, Apr 15, 2013 at 05:04:16PM +0100, Simon Riggs wrote: > On 15 April 2013 16:55, Tom Lane <tgl@sss.pgh.pa.us> wrote: > > Simon Riggs <simon@2ndQuadrant.com> writes: > >> On 15 April 2013 16:24, David Fetter <david@fetter.org> wrote: > >>> Do you have numbers on this, or ways to gather same? In other > >>> words, how do we know what resources (time, CPU cycles, disk > >>> seeks, etc.) are being consumed here? > > > >> The multi-insert optimisation for COPY is already there and works > >> well enough to have been committed. > > > > You seem to not have answered the question. Exactly what sort of > > performance gain might be possible, bearing in mind that anything > > that invokes a trigger (for instance) is unlikely to be amazingly > > fast anyway? > > Forgive me, I assumed the list would be familiar with the > optimization and so be excited by the need for this. > > I will implement as a kluge, test and report the results. > > Loading data into a table with a SERIAL or UUID column is the main > use case, so I'll measure that. The former is common enough a use case to optimize specifically, should the numbers come out right. Do you suppose that an in-core UUID generator would help the latter make more sense as a part of the same use case? Cheers, David. -- David Fetter <david@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter@gmail.com iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate
В списке pgsql-hackers по дате отправления: