| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: \gexec \watch |
| Date: | 2018-12-06 08:01:26 |
| Message-ID: | 20181206080126.jl3tbw2odeqcpz2j@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2018-Dec-06, David Fetter wrote:
> There's a bit of a philosophical issue here, or a mathematical one,
> whichever way you want to put it. Does it actually make sense to have
> the behavior of one "semicolon" spill onto another?
Honestly, I don't see the mathematicality in this. It either works, or
it doesn't -- and from my POV right now it doesn't. Are you saying we
need a \gexecwatch for this to work?
I can of course solve my problem with a simple python program, but psql
is so close ...
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2018-12-06 08:25:41 | Re: speeding up planning with partitions |
| Previous Message | Alvaro Herrera | 2018-12-06 07:57:26 | Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 |