Re: \pset xheader_width page as default? (Re: very long record lines in expanded psql output)

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: \pset xheader_width page as default? (Re: very long record lines in expanded psql output)
Дата
Msg-id CAFj8pRBehZU4jZMQ7NieunSG4xOgsQXh9_zDQtirpKOyJYdO3Q@mail.gmail.com
обсуждение исходный текст
Ответ на Re: \pset xheader_width page as default? (Re: very long record lines in expanded psql output)  (Christoph Berg <myon@debian.org>)
Ответы Re: \pset xheader_width page as default? (Re: very long record lines in expanded psql output)  (Pavel Stehule <pavel.stehule@gmail.com>)
Список pgsql-hackers


út 30. 8. 2022 v 16:36 odesílatel Christoph Berg <myon@debian.org> napsal:
Re: Pavel Stehule
> pspg requires all lines to have the same width. It can do some corrections
> - but it is hard to detect wanted differences or just plain text format.
>
> can be nice to have the first invisible row with some information about
> used formatting. pspg does some heuristic but this code is not nice and it
> is fragile.

I like pspg and use it myself, but I don't think a tool that does the
right thing by hiding a full screen of ---- from the user should
hinder making the same progress in psql with a simple pager.

ASCII allows to set some metadata, that should be invisible in all correctly implemented pagers.

 

Christoph

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Christoph Berg
Дата:
Сообщение: Re: \pset xheader_width page as default? (Re: very long record lines in expanded psql output)
Следующее
От: Aleksander Alekseev
Дата:
Сообщение: Re: Convert *GetDatum() and DatumGet*() macros to inline functions