Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gAgrH-0007xj-Rf for pgsql-docs@arkaria.postgresql.org; Thu, 11 Oct 2018 19:42:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gAgrF-0001bg-NA for pgsql-docs@arkaria.postgresql.org; Thu, 11 Oct 2018 19:42:53 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gAg2S-0002ud-44 for pgsql-docs@lists.postgresql.org; Thu, 11 Oct 2018 18:50:24 +0000 Received: from mail-oi1-x231.google.com ([2607:f8b0:4864:20::231]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gAg2P-0003EZ-Gp for pgsql-docs@lists.postgresql.org; Thu, 11 Oct 2018 18:50:22 +0000 Received: by mail-oi1-x231.google.com with SMTP id j68-v6so7906903oib.7 for ; Thu, 11 Oct 2018 11:50:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3HwYGvmafxUy8bk5L+42ZGbBM8eRWfgwTeosnMv+Xog=; b=LxNTb2sgi0XJNTmO1OxLuzCYLUuFBa5bSJiOuSajH7WbJJDEXmG0WpaFdjOiye9NvA FLpHR6sPcYOSUNTtSCGxw/2zyImp/NVhOoFB5+/aSAkpC8peCeaZ10pVBkOkKb3CF0Yh 8hMzeqN57nXu6lSXX3L3IQ2rEm+mVqYnSk523JNe1qZAB2lGaNZaK2lSDnnKsbSIm0t8 cEXAur9WCDhJn3OSG6aW21flqrpdo/ELJu8kEUp2neSgdpM1S/rLw2ikZ/BLJSAci8aX CCgPZS0I9cga48SrpMfBpqE1gTf1uUlYM9bvo0AT/tKl5I/3GzLHrtaGRNS8UHEo+9Sq U8zQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3HwYGvmafxUy8bk5L+42ZGbBM8eRWfgwTeosnMv+Xog=; b=X7lGH+xamix2H4n1HuSn1mjAv5IGmLZbDuM125btkDqQ96TfghyJThcooS9AksihAd ZyJ6f9dEwvUvQ5dB1ee3yk1RHdrkqPdVVwMp/8sN5EJ8F7Rz6qXfWLjwxhMV/FSW7nun htcaofhZpex8OXxtsvVI2vfojogdfWYQSGzhFkCZm3fKZmaTRRLAm8dHXjAb89BixDUO 26P+0XV5fDtJDGyIAJA3mwjseROu6quqXQQwLbxFG/f9sXMKmue9z9gJutnlckh+e5ps hxildK1EDmdD5Rm50rL56f1wscvHYa8qoGJmst80wf+XnlQ6YqywBLU6QBHpyq3fNHpL 51pQ== X-Gm-Message-State: ABuFfoh/43Q9XkjUbY1I04UDxZuxjV0VnVhd3kNqMVCn+keJADZwQ8z1 vrGE+OT3tz8PCX1Z6YdkKfoJnGZCPjKHih7pYzQ= X-Google-Smtp-Source: ACcGV63UZvh3U33dlEPD3M6KbngjinfHmY9lfMlmI+TGyChFglO8QpCKYXC0qGcZnPzDrGcKYKjIlKoj+oltWPXgN20= X-Received: by 2002:a54:4d8b:: with SMTP id y11-v6mr1617036oix.168.1539283820834; Thu, 11 Oct 2018 11:50:20 -0700 (PDT) MIME-Version: 1.0 References: <153653649616.23138.1453197444453120513@wrigleys.postgresql.org> <20181010195959.GB7806@momjian.us> In-Reply-To: <20181010195959.GB7806@momjian.us> From: Peter Krauss Date: Thu, 11 Oct 2018 15:50:09 -0300 Message-ID: Subject: Re: please inform data_directory To: bruce@momjian.us Cc: pgsql-docs@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000597c530577f871eb" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000597c530577f871eb Content-Type: text/plain; charset="UTF-8" Hi, trying to explain again, the "SHOW data_directory" is an information that *not exist in the guide today, *but must to exist... is a suggestion to add information, a middle-expert or non-extert reader need it. On Wed, Oct 10, 2018 at 4:59 PM Bruce Momjian wrote: > On Sun, Sep 9, 2018 at 11:41:36PM +0000, PG Doc comments form wrote: > > The following documentation comment has been logged on the website: > > > > Page: https://www.postgresql.org/docs/10/static/functions-admin.html > > Description: > > > > It is impossible to use pg_read_file(), etc. functions without > > SHOW data_directory > > What do you mean by that? I can call pg_read_file() before calling > 'SHOW data_directory'. Are you saying that pg_read_file can only read > in the data_directory? It is designed that way. > > -- > Bruce Momjian http://momjian.us > EnterpriseDB http://enterprisedb.com > > + As you are, so once was I. As I am, so you will be. + > + Ancient Roman grave inscription + > --000000000000597c530577f871eb Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi, trying to explain again,=C2=A0
the "SHOW=C2= =A0 data_directory"=C2=A0 is an information that=C2=A0not exist in = the guide today,=C2=A0but must to=C2=A0exist... is a suggestion to add = information, a middle-expert or non-extert reader need it.


On Wed, Oct 10, 2018 at= 4:59 PM Bruce Momjian <bruce@momjia= n.us> wrote:
On Sun, Sep=C2= =A0 9, 2018 at 11:41:36PM +0000, PG Doc comments form wrote:
> The following documentation comment has been logged on the website: >
> Page: https://www.postgresql.org/= docs/10/static/functions-admin.html
> Description:
>
> It is impossible to use pg_read_file(), etc. functions without
> SHOW=C2=A0 data_directory

What do you mean by that?=C2=A0 I can call pg_read_file() before calling 'SHOW=C2=A0 data_directory'.=C2=A0 Are you saying that pg_read_file= can only read
in the data_directory?=C2=A0 It is designed that way.

--
=C2=A0 Bruce Momjian=C2=A0 <bruce@momjian.us>=C2=A0 =C2=A0 =C2=A0 =C2=A0 http://momjian.us
=C2=A0 EnterpriseDB=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0
http://enterprisedb.com
+ As you are, so once was I.=C2=A0 As I am, so you will be. +
+=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 Ancient Roman grave inscription +
--000000000000597c530577f871eb--