Re: Seg fault in pgbench
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Jeff Janes <jeff.janes@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>,
Fabien COELHO <coelho@cri.ensmp.fr>
Date: 2016-02-12T20:22:59Z
Lists: pgsql-hackers
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. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
pgbench: fix segfault with empty sql file
- db94419ffd68 9.6.0 landed
-
pgbench: improve multi-script support
- 8bea3d221984 9.6.0 cited