Re: very long record lines in expanded psql output

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Platon Pronko <platon7pronko(at)gmail(dot)com>
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-23 19:28:04
Message-ID: 15de79ff-b872-498f-8b9c-ced62f460936@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 8/23/21 2:00 PM, Platon Pronko wrote:
> Hi!
>
> Apparently I did forget something, and that's the patch itself :)
> Thanks for Justin Pryzby for pointing this out.
>
> Attaching the patch now.
>
>

(Please avoid top-posting on PostgreSQL lists)

This patch seems basically sound. A couple of things:

1. It's not following project indentation style (BSD brace placement)

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.

cheers

andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2021-09-23 19:29:08 Re: Recent cpluspluscheck failures
Previous Message Tom Lane 2021-09-23 19:24:16 Re: Recent cpluspluscheck failures