From: Platon Pronko <platon7pronko@gmail.com>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: very long record lines in expanded psql output
Date: Thu, 5 Aug 2021 14:14:18 +0300
Message-ID: <27f30f68-c4bd-2f02-080c-8feb0b6eded3@gmail.com> (raw)
In-Reply-To: <CAFj8pRBJ8bcTga9qTYG_v25BfeCB=4+GNc1rbf94qex_3C_e-A@mail.gmail.com>
References: <f03d38a3-db96-a56e-d1bc-dbbc80bbde4d@gmail.com>
<CAFj8pRBJ8bcTga9qTYG_v25BfeCB=4+GNc1rbf94qex_3C_e-A@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: platon7pronko@gmail.com, pavel.stehule@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: very long record lines in expanded psql output
In-Reply-To: <27f30f68-c4bd-2f02-080c-8feb0b6eded3@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox