Re: File truncation within PostgresNode::issues_sql_like() wrong on Windows
Andrew Dunstan <andrew@dunslane.net>
From: Andrew Dunstan <andrew@dunslane.net>
To: Michael Paquier <michael@paquier.xyz>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-04-17T13:55:47Z
Lists: pgsql-hackers
On 4/17/21 9:04 AM, Michael Paquier wrote: > On Thu, Apr 15, 2021 at 09:12:52PM -0400, Andrew Dunstan wrote: >> It's worked on fairywren, I will double check on drongo and if all is >> well will commit. > Thanks Andrew. For the archive's sake, this has been committed as of > 3c5b068. > > While reading the commit, I have noticed that you used SEEK_SET > instead of 0 as I did in my own patch. That makes the code easier to > understand. Could it be better to apply the same style to all the > perl scripts doing some seek() calls? Please see the attached. Yes please, much better to use a symbolic name rather than a magic number. I wouldn't bother backpatching it though. cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com
Commits
-
Replace magic constants for seek() calls in perl scripts
- c731f9187b5f 14.0 landed
-
Allow TestLib::slurp_file to skip contents, and use as needed
- d48212c45202 9.6.22 landed
- f8ba416a98ce 10.17 landed
- 4c9298130ae8 11.12 landed
- d380ec9891db 12.7 landed
- e480c6dd33f4 13.3 landed
- 3c5b0685b921 14.0 landed