Re: Improve error reporting in 027_stream_regress test - Mailing list pgsql-hackers

From Nazir Bilal Yavuz
Subject Re: Improve error reporting in 027_stream_regress test
Date
Msg-id CAN55FZ3-q0rp=gEg=M_UwQhJ1dWmCY30PdAXrnxPQcd1Uc__9Q@mail.gmail.com
Whole thread Raw
In response to Re: Improve error reporting in 027_stream_regress test  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Improve error reporting in 027_stream_regress test
List pgsql-hackers
Hi,

On Sat, 19 Jul 2025 at 09:06, Michael Paquier <michael@paquier.xyz> wrote:
>
> This one looks acceptable to me, so applied to begin with something,
> splitting things into two pieces for clarity with some tweaks.  I have
> changed things to use system_log() at the end, with fat-commas to link
> the long options and their arguments.

Thanks!

I realized that we actually don't trim the file, we do the opposite;
read the file from both ends. Sorry for not realizing earlier. I will
update the remaining patches according to that but I think trim_file()
is helpful, too. What do you think about adding both

```
trim_file() -> trims $n lines from head or tail of the file and
returns the remaining lines.
read_file_ends() -> returns $n lines from head or tail of the file.
```

although trim_file() will not be used in these particular patches?

-- 
Regards,
Nazir Bilal Yavuz
Microsoft



pgsql-hackers by date:

Previous
From: vignesh C
Date:
Subject: Re: Logical Replication of sequences
Next
From: jian he
Date:
Subject: Re: sql/json query function JsonBehavior default expression's collation may differ from returning type's collation