On Thu, Oct 11, 2018 at 12:43 PM Peter Krauss <ppkra...@gmail.com> wrote:
> > The page https://www.postgresql.org/docs/10/static/functions-admin.html > need this information, is like a "pg_read_file Guide". > Applies to all: "The functions shown in Table 9.88 provide native access to files on the machine hosting the server. Only files within the database cluster directory and the log_directory can be accessed. Use a relative path for files in the cluster directory, and a path matching the log_directory configuration setting for log files. Use of these functions is restricted to superusers except where stated otherwise." Applies to pg_read_file: "pg_read_file returns part of a text file, starting at the given offset, returning at most length bytes (less if the end of file is reached first). If offset is negative, it is relative to the end of the file. If offset and length are omitted, the entire file is returned. The bytes read from the file are interpreted as a string in the server encoding; an error is thrown if they are not valid in that encoding." There is nothing unclear there and by the time one gets to this part of the documentation its reasonably assumed they understand "data directory"; being verbose on that point is not an improvement. For the rare person that gets confused these lists are available to obtain clarity. But aside from the one comment I've already made - and this is very minor in nature - I'm not seeing anything obvious short-comings here. David J.
