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>, Zhihong Yu <zyu(at)yugabyte(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: very long record lines in expanded psql output
Date: 2022-07-25 18:27:22
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2021-10-03 Su 16:03, Platon Pronko wrote:
>> Hi,
>> +               pg_log_error("\\pset: allowed xheader_width values
>> are full
>> (default), column, page, or an number specifying exact width.");
>>   an number specifying -> a number specifying
>> Cheers
> Fixed, attaching the updated patch. Thank you!

Committed. There were a couple of bits missing, which I filled in, and I
changed the behaviour when the option is given without an argument, so
that instead of resetting it the current value is shown, similarly to
how most pset options work.



Andrew Dunstan

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2022-07-25 19:04:19 Re: optimize lookups in snapshot [sub]xip arrays
Previous Message Joe Conway 2022-07-25 17:30:43 Re: Proposal to provide the facility to set binary format output for specific OID's per session