| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: psql --batch |
| Date: | 2017-08-28 06:56:43 |
| Message-ID: | alpine.DEB.2.20.1708280847540.9003@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I find myself regurgitating the incantation
>
> psql -qAtX -v ON_ERRORS_STOP=1
>
> quite a bit. It's not ... super friendly.
>
> It strikes me that we could possibly benefit from a 'psql --batch' option.
>
> Thoughts?
The link between -qAtX and "batch" is not that fully obvious, especially
the unaligned tuples-only part. If so, why not some -F <tab> as well?
ISTM that the real pain is the "-v ON_ERRORS_STOP=1" which I occasionally
encountered as well, the other one letter ones are not too bad. Maybe it
would be enough to have a shortcut for this one, say "-B"?
alias?
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2017-08-28 06:57:52 | Re: Re: Poor cost estimate with interaction between table correlation and partial indexes |
| Previous Message | Mithun Cy | 2017-08-28 06:39:46 | NoMovementScanDirection in heapgettup() and heapgettup_pagemode() |