On Wed, Jan 18, 2017 at 3:06 AM, Gilles Darold <gilles.dar...@dalibo.com> wrote:
> This have already been discuted previously in this thread, one of my
> previous patch version has implemented this behavior but we decide that
> what we really want is to be able to use the function using the
> following simple query:
>
> SELECT pg_read_file(pg_current_logfiles());
>
> and not something like
>
> SELECT pg_read_file(SELECT file FROM pg_current_logfiles() LIMIT 1);
> or
> SELECT pg_read_file(SELECT file FROM pg_current_logfiles() WHERE
> method='stderr');
>
> You can also obtain the "kind" of output from the SRF function using:
>
> SELECT pg_read_file('current_logfiles');
I don't really understand this argument as you can do that as well:
SELECT pg_read_file(file) FROM pg_current_logfiles WHERE method = 'stderr';
> I'm not against adding a warning or error message here even if it may
> never occurs, but we need a new error code as it seems to me that no
> actual error code can be used.
ERRCODE_INTERNAL_ERROR, no?
--
Michael
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
