Re: very long record lines in expanded psql output - Mailing list pgsql-hackers

From Platon Pronko
Subject Re: very long record lines in expanded psql output
Date
Msg-id 784205fd-ca87-68df-983c-b1c94ad9d6f0@gmail.com
Whole thread Raw
In response to Re: very long record lines in expanded psql output  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: very long record lines in expanded psql output  (Zhihong Yu <zyu@yugabyte.com>)
List pgsql-hackers
On 2021-09-24 14:42, Andrew Dunstan wrote:
> 
> On 9/24/21 12:49 AM, Platon Pronko wrote:
>> On 2021-09-23 22:28, Andrew Dunstan wrote:
>>>
>>> 2. It would possibly be better to pass the relevant parts of the options
>>> to print_aligned_vertical_line() rather than the whole options
>>> structure. It feels odd to pass both that and opt_border.
>>
>> What do you think about doing it the other way around - passing only
>> whole
>> options structure? That way we will roll 4 parameters (opt_border,
>> printTextFormat,
>> and two xheader ones) into only one argument.
>> This increases code coupling a bit, but I'm not sure if that's
>> relevant here.
>>
> 
> Sure, as long as it doesn't result in duplicated computation.

Hi!

Please find attached the updated patch - with fixed braces and
adjusted parameters to print_aligned_vertical_line().

Best regards,
Platon Pronko
Attachment

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set
Next
From: wenjing
Date:
Subject: Re: [Proposal] Global temporary tables