Re: pgbench -f and vacuum - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pgbench -f and vacuum
Date
Msg-id CA+TgmoZf6ngRjjL4EsbE7i15p5hBfgm-ZJt_zmNBXtvVvDXn9A@mail.gmail.com
Whole thread Raw
In response to Re: pgbench -f and vacuum  (Stephen Frost <sfrost@snowman.net>)
Responses Re: pgbench -f and vacuum  (Stephen Frost <sfrost@snowman.net>)
Re: pgbench -f and vacuum  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On Tue, May 12, 2015 at 12:08 PM, Stephen Frost <sfrost@snowman.net> wrote:
> * Robert Haas (robertmhaas@gmail.com) wrote:
>> It's says:
>>
>> starting vacuum.... ERROR: blah
>> ERROR: blah
>> ERROR: blah
>> done
>>
>> And then continues on.  Sure, that's not the greatest error reporting
>> output ever, but what do you expect from pgbench?  I think it's clear
>> enough what's going on there.  The messages appear in quick
>> succession, because it doesn't take very long to notice that the table
>> isn't there, so it's not like you are sitting there going "wait,
>> what?".
>>
>> If we're going to add something, I like your second suggestion
>> "(ignoring this error and continuing anyway)" more than the first one.
>> Putting "ignoring:" before the thing you plan to ignore will be
>> confusing, I think.
>
> +1 to adding "(ignoring this error and continuing anyway)" and
> committing this.

You want to take care of that?

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



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: pgbench -f and vacuum
Next
From: Stephen Frost
Date:
Subject: Re: pgbench -f and vacuum