Re: pg_execute_from_file, patch v10 - Mailing list pgsql-hackers

From Itagaki Takahiro
Subject Re: pg_execute_from_file, patch v10
Date
Msg-id AANLkTi=fGV6G_J9x7ujtgywf_N1RRGAP4j0jphXmuuDa@mail.gmail.com
Whole thread Raw
In response to Re: pg_execute_from_file, patch v10  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: pg_execute_from_file, patch v10  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Wed, Dec 15, 2010 at 12:20, Robert Haas <robertmhaas@gmail.com> wrote:
> It seems like pg_read_binary_file() is good to have regardless of
> whatever else we decide to do here.  Should we pull that part out and
> commit it separately?

OK, I'll do that, but I have some questions:#1 Should we add 'whole' versions of read functions in Dimitri's work?#2
Shouldwe allow additional directories? In the discussion,   no restriction seems to be a bad idea. But EXTENSION
requires  to read PGSHARE or some system directories? 

#2 can be added separately from the first change,
but I'd like to add #1 at the same time if required.

Or, if we're planning not to use pg_read_file functions in the
EXTENSION patch, we don't need #2 anyway.

--
Itagaki Takahiro


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: CommitFest wrap-up
Next
From: Alvaro Herrera
Date:
Subject: Re: Getting "ERROR: no unpinned buffers available" on HEAD, should I investigate?