| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Jaime Casanova <jaime(at)2ndquadrant(dot)com>, depesz(at)depesz(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Enhanced psql in core? |
| Date: | 2011-07-10 16:51:15 |
| Message-ID: | 2946.1310316675@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
>> 2011/7/10 Jaime Casanova <jaime(at)2ndquadrant(dot)com>:
>>> big part of this seems to be (based on the examples on the page,
>>> haven't read the patch) scripting functionality but now that we have
>>> DO, is really a need for that?
> note - a output from DO statement is limited to RAISE statement - you
> can't send back a SELECT's result
You can't *today*. But it's a very good question whether it wouldn't
make more sense to solve these problems by extending DO rather than
adding things into psql. Functionality in DO will be available to
non-psql clients.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-07-10 17:28:37 | Re: Expression Pruning in postgress |
| Previous Message | Steve Singer | 2011-07-10 16:20:39 | Re: Online base backup from the hot-standby |