Re: [PATCH] Tab completion for ALTER DATABASE … SET TABLESPACE - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [PATCH] Tab completion for ALTER DATABASE … SET TABLESPACE
Date
Msg-id 20180922015701.t3bqikno7c3xhqwx@alap3.anarazel.de
Whole thread Raw
In response to Re: [PATCH] Tab completion for ALTER DATABASE … SET TABLESPACE  (Thomas Munro <thomas.munro@enterprisedb.com>)
List 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


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [PATCH] Tab completion for ALTER DATABASE … SET TABLESPACE
Next
From: Chapman Flack
Date:
Subject: Re: vary read_only in SPI calls? or poke at the on-entry snapshot?