Skip site navigation (1) Skip section navigation (2)

Re: Simulating Clog Contention

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: Abhijit Menon-Sen <ams(at)toroid(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Simulating Clog Contention
Date: 2012-01-30 17:26:31
Message-ID: CA+TgmoZ_1U=ngCM-D3kyG2XPPrHoNLzJhVQZOR9BUVxbLdiRTA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Mon, Jan 30, 2012 at 10:53 AM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> On Thu, Jan 26, 2012 at 6:18 AM, Abhijit Menon-Sen <ams(at)toroid(dot)org> wrote:
>> At 2012-01-12 12:31:20 +0000, simon(at)2ndQuadrant(dot)com wrote:
>>>
>>> The following patch adds a pgbench option -I to load data using
>>> INSERTs
>>
>> This is just to confirm that the patch applies and builds and works
>> fine (though of course it does take a long time… pity there doesn't
>> seem to be any easy way to add progress indication like -i has).
>
> I was thinking the opposite.  That -i should only print progress
> indication when -d is given.  Or at least knock an order of magnitude
> or two off of how often it does so.

I'd be in all in favor of having -i emit progress reports 10x less
often; even on a laptop, the current reports are very chatty.  But I
think 100x less often might be taking it too far.

Either way, if we're going to have an option for inserts, they should
produce the same progress reports that COPY does - though possibly
more often, since I'm guessing it's likely to be way slower.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2012-01-30 17:28:46
Subject: Re: Simulating Clog Contention
Previous:From: hubert depesz lubaczewskiDate: 2012-01-30 17:23:15
Subject: Re: pg_dump -s dumps data?!

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group