Re: Add \i option to bring in the specified file as a quoted literal - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Add \i option to bring in the specified file as a quoted literal
Date
Msg-id 20131112160703.GK15562@momjian.us
Whole thread Raw
In response to Re: Add \i option to bring in the specified file as a quoted literal  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Add \i option to bring in the specified file as a quoted literal  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Wed, Oct 23, 2013 at 10:31:39AM +0530, Amit Kapila wrote:
> On Tue, Oct 22, 2013 at 3:04 AM, Piotr Marcinczyk <pmarcinc@gmail.com> wrote:
> > Hi,
> >
> > I would like to implement item from TODO marked as easy: "Add \i option
> > to bring in the specified file as a quoted literal". I understand intent
> > of this item, to be able to have parts of query written in separate
> > files (now it is impossible, because \i tries to execute content of file
> > as a separate command by function process_file).
> 
> For the usecase discussed in the mail chain of that TODO item, Robert
> Haas has provided an alternative to achieve it, please check below
> link:
> http://www.postgresql.org/message-id/AANLkTi=7C8xFYF7uQW0y+si8oNdKoY2NX8jc4bU0GWvY@mail.gmail.com
> 
> If you think that alternative is not sufficient for the use case, then
> adding new option/syntax is worth, otherwise it might be a shortcut or
> other form of some existing way which can be useful depending on how
> frequently users use this syntax.

So, can we remove this TODO item?

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + Everyone has their own god. +



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Patch for fail-back without fresh backup
Next
From: Kohei KaiGai
Date:
Subject: Re: What's needed for cache-only table scan?