Re: File truncation within PostgresNode::issues_sql_like() wrong on Windows - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: File truncation within PostgresNode::issues_sql_like() wrong on Windows
Date
Msg-id 7ec96575-bd2a-0593-3e93-ffe955a7c78c@dunslane.net
Whole thread Raw
In response to Re: File truncation within PostgresNode::issues_sql_like() wrong on Windows  (Michael Paquier <michael@paquier.xyz>)
Responses Re: File truncation within PostgresNode::issues_sql_like() wrong on Windows  (Michael Paquier <michael@paquier.xyz>)
List 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




pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Table refer leak in logical replication
Next
From: Pavel Stehule
Date:
Subject: proposal - log_full_scan