| From: | Platon Pronko <platon7pronko(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: very long record lines in expanded psql output |
| Date: | 2021-08-05 18:56:20 |
| Message-ID: | 3d337f89-d7db-2198-2a7c-a7ce58b94ce8@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> it can be a fully new format - designed for simple copy from terminal. Some
> like
>
> ====== record: 10 ======
> ------------ proname ------------
> left
> ------------ prosrc ------------
> $lalalal
> ewqrwqerw
> ewqrwqerqrewq
> $
> ===============
> no, it was proposed for psql
How is this better than "copy (...) to stdout"? E.g.:
$ copy (select * from pg_class limit 1) to stdout;
2619 pg_statistic 11 12016 0 10 2 2619 0 18 402 18 2840 t f p r 31 0 f f f f f t n f0 478 1 {postgres=arwdDxt/postgres} \N \N
You can still copy the necessary parts (using mouse selection) -
seems that it achieves the the same goal.
Best regards,
Platon Pronko
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2021-08-05 19:08:56 | Re: very long record lines in expanded psql output |
| Previous Message | Pavel Stehule | 2021-08-05 18:50:09 | Re: very long record lines in expanded psql output |