| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Arthur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Tab completion for ALTER DATABASE … SET TABLESPACE |
| Date: | 2018-09-22 01:57:01 |
| Message-ID: | 20180922015701.t3bqikno7c3xhqwx@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2018-09-22 09:56:00 +1200, Thomas Munro wrote:
> I vote for doing it this way then. It may turn out to be useful for
> efficient SearchSysCache(...), DirectFunctionCall(...) and other
> things like that.
Yea, especially the *FunctionCall* stuff is awfully verbose.
I also wonder if it could make
http://archives.postgresql.org/message-id/20180605172952.x34m5uz6ju6enaem%40alap3.anarazel.de
a bit less painful.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chapman Flack | 2018-09-22 02:26:02 | Re: vary read_only in SPI calls? or poke at the on-entry snapshot? |
| Previous Message | Andres Freund | 2018-09-22 01:52:28 | Re: [PATCH] Tab completion for ALTER DATABASE … SET TABLESPACE |