Re: pgbench failed when -f option contains a char '@'
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: "Wang, Shenhao" <wangsh.fnst@cn.fujitsu.com>,
"pgsql-hackers@lists.postgresql.org"
<pgsql-hackers@lists.postgresql.org>
Date: 2020-12-18T15:10:42Z
Lists: pgsql-hackers
Heikki Linnakangas <hlinnaka@iki.fi> writes: > I think we should just leave this as it is. The user can simply rename > the file. Yeah. The assumption when we defined the script-weight syntax was that there's no particular reason to use "@" in a script file name, and I don't see why that's a bad assumption. > Or maybe one change would be worthwhile here: First check if the part > after the @ contains only digits. If doesn't, then assume it's part of > the filename rather than a weight. That would fix this for cases like > "foo@1.sql", although not for "foo@1". I do not like introducing ambiguity of that sort. Not being entirely clear on which script file is going to be read seems like a recipe for security issues. regards, tom lane
Commits
-
Doc: improve description of pgbench script weights.
- fafc6f716ade 10.16 landed
- c7a0b94c4528 9.6.21 landed
- 3989fdab48d9 12.6 landed
- 22d1569af95d 13.2 landed
- 1990ce186ee6 14.0 landed
- 14c6afbbb308 11.11 landed