Subject: Re: very long record lines in expanded psql output
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
References: <f03d38a3-db96-a56e-d1bc-dbbc80bbde4d@gmail.com>
 <CAFj8pRBJ8bcTga9qTYG_v25BfeCB=4+GNc1rbf94qex_3C_e-A@mail.gmail.com>
From: Platon Pronko <platon7pronko@gmail.com>
Message-ID: <27f30f68-c4bd-2f02-080c-8feb0b6eded3@gmail.com>
Date: Thu, 5 Aug 2021 14:14:18 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: 
 <CAFj8pRBJ8bcTga9qTYG_v25BfeCB=4+GNc1rbf94qex_3C_e-A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/27f30f68-c4bd-2f02-080c-8feb0b6eded3%40gmail.com>
Precedence: bulk

Hi!

pspg looks nice :)

> Your proposal breaks pspg
> 
> https://github.com/okbob/pspg

I tried the following (after the patch):

./psql template1 -c "select n, repeat('x', n) as long_column_name from unnest(array[42,210]) as n" | pspg

And it seems that pspg handled the situation without any issue. Also I tried inserting newlines into the output, and pspg still performed without issue. Can you give an example of scenario which should break after changing the record header length?

Best regards,
Platon Pronko