Re: File truncation within PostgresNode::issues_sql_like() wrong on Windows

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: File truncation within PostgresNode::issues_sql_like() wrong on Windows
Date: 2021-04-17 13:55:47
Message-ID: 7ec96575-bd2a-0593-3e93-ffe955a7c78c@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2021-04-17 14:36:52 proposal - log_full_scan
Previous Message Amit Kapila 2021-04-17 13:32:00 Re: Table refer leak in logical replication