Re: very long record lines in expanded psql output

From: Platon Pronko <platon7pronko(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Justin Pryzby <pryzby(at)telsasoft(dot)com>
Subject: Re: very long record lines in expanded psql output
Date: 2021-09-24 04:49:32
Message-ID: 7bbc7e80-ca37-b601-9081-68d2e84b42af@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Best regards,
Platon Pronko

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2021-09-24 04:59:02 Re: Added schema level support for publication.
Previous Message Greg Nancarrow 2021-09-24 04:38:10 Re: Skipping logical replication transactions on subscriber side