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

From Amit Kapila
Subject Re: Add \i option to bring in the specified file as a quoted literal
Date
Msg-id CAA4eK1J6374maQefLFr1ZkUrT8ZAE7sOqO=FMbfjjXf_L5XZWg@mail.gmail.com
Whole thread Raw
In response to Add \i option to bring in the specified file as a quoted literal  (Piotr Marcinczyk <pmarcinc@gmail.com>)
Responses Re: Add \i option to bring in the specified file as a quoted literal  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
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.

With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Compression of full-page-writes
Next
From: Florian Weimer
Date:
Subject: Re: Why the asprintf patch is still breaking the buildfarm