Re: Seg fault in pgbench - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: Seg fault in pgbench
Date
Msg-id CAMkU=1z_WUfQ_ygwvDwE9mM4XOiv71yECSTayqnGVaqWAvjnvQ@mail.gmail.com
Whole thread Raw
In response to Re: Seg fault in pgbench  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Fri, Feb 12, 2016 at 12:22 PM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> Jeff Janes wrote:
>> If I give pgbench an empty file, I get a segfault.
>>
>> $ touch empty.sql
>> $ src/bin/pgbench/pgbench -T 60 -f empty.sql
>> starting vacuum...end.
>> Segmentation fault (core dumped)
>
> I fixed this by checking whether the first command is NULL; originally
> this case was handled by checking whether the command list itself was
> NULL.  It could also be fixed by having process_file() return NULL in
> the case of an command-less file, but it seemed more churn for no actual
> reason, since the case is going to be rejected by exiting the program
> anyway.
>

Looks good.  Thanks.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution.
Next
From: Joe Conway
Date:
Subject: Re: NextXID format change (was Re: exposing pg_controldata and pg_config as functions)