Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e2RQm-0006IT-45 for pgsql-docs@arkaria.postgresql.org; Thu, 12 Oct 2017 00:32:56 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1e2RQl-0007FX-N1 for pgsql-docs@arkaria.postgresql.org; Thu, 12 Oct 2017 00:32:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e2RQO-0006Yr-Aq for pgsql-docs@postgresql.org; Thu, 12 Oct 2017 00:32:32 +0000 Received: from mail-pf0-x22a.google.com ([2607:f8b0:400e:c00::22a]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1e2RQK-0003mK-HR for pgsql-docs@postgresql.org; Thu, 12 Oct 2017 00:32:31 +0000 Received: by mail-pf0-x22a.google.com with SMTP id z11so2599584pfk.4 for ; Wed, 11 Oct 2017 17:32:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=V9ipnvaBH7NMUbJI0yeE9CUWK6NXe79ZIZ1DuxOjatk=; b=HApAR+WTIBEoTL7zVB+IDjXpwQSbXlNO8k2CCzNtVR1ZXO9pptCfZGiRlSwts17wHH F3wFGfwzviqMa9Yyb0k6LVDocu9WfCv6Epp5W/8Wyj+LXc1k/S27l09SkvWOmAIT3KPS iPh+Sws089MdmVZ78fr60JKnmnvqNsARqydUrrko1I8GYUc1UA7Ol1nkJnUCzKUGcJQ9 02gv+6AMywJ9DbWWF3yJkwnVCVfGhpquLvk0jLgRUTSGk+7i2uw4rtc2hp2KXv+9drjU 1j/1yv5XJGS97c36rQZUZJitzCIB3u3xqd0wqtlTc1hnJKfRdMUiObHsm0LQXtgOViSa t4Vg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=V9ipnvaBH7NMUbJI0yeE9CUWK6NXe79ZIZ1DuxOjatk=; b=D84R2YRW5nml1Oyn7RM5SFwVQY5MpYGZqwWQ8bmnUi4MOPtL1EaD+ATnbcu+oULy21 rRwhGflZgu+PyyJIblvteEHKqe6owxaJjwmf1bPwgIt+sZsvMJgtrwkgENKJlN8dPPH8 Bt/IO7dapEMRpYCakK33TcPWmC00KbGST8wz4rRXb2XdvNQC8q3wLFJnt9btBprmx6Mo ISmjt3kAjx7GXFuoLtNEK2fQ8ExPce0Vk4eBXinzThzunfUkE5Se+EksIc90UZD4whZj GFq+cFxQAefooTk5+lBzep4oyoSoopV2C3FMuDbw6JBY8yGPuzywr2m+HXXTOX6rwpun advg== X-Gm-Message-State: AMCzsaX1Wr269VWs5OBLFsypBgz/ST+FipZIPVQk0FP/4sVDOvfTgGAu egPtLnGpFdH0HxJoz28NmbshgEPcvNk8hsg4CNKNj3Usg5/3UVbHMkDg7uyIqEy3YVBpVcxd47G XVA96n4o2gE3J0W21Y6FqD59W0wfcnrM7yDQd43lotggaobO/GfUU7wAMm9atgjRIai9Mi2+2Wy 6KjBk= X-Google-Smtp-Source: AOwi7QCray+JlR9LjEbNUg2e8MYhx1TxU8pNallQeI8OGl7xOnIIR2mGSRNjdhan6iJx2Zbd4gKogw== X-Received: by 10.98.24.20 with SMTP id 20mr641498pfy.71.1507768345865; Wed, 11 Oct 2017 17:32:25 -0700 (PDT) Received: from osaka.octopusnet (p370046-ipngn12701marunouchi.tokyo.ocn.ne.jp. [153.201.169.46]) by smtp.gmail.com with ESMTPSA id o9sm14382526pfk.162.2017.10.11.17.32.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Oct 2017 17:32:24 -0700 (PDT) Subject: Re: 19.2. File Locations doesn't tell you the file locations! To: redirect.null@gmail.com Cc: "David G. Johnston" , "pgsql-docs@postgresql.org" References: <20171006100649.14645.41518@wrigleys.postgresql.org> From: Ian Barwick Message-ID: <4a684d34-20e1-6aab-999d-ec2a9b46ebb5@2ndquadrant.com> Date: Thu, 12 Oct 2017 09:32:21 +0900 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org On 10/10/2017 11:46 PM, David G. Johnston wrote: > On Fri, Oct 6, 2017 at 3:06 AM, >wrote: > > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/10/static/runtime-config-file-locations.html > Description: > > In the latest documentation "Section 19.2. File Locations" tells you how to > set the locations of the various config files, but it doesn't tell you how > to find out where they bloody well are in the first place! Which seems like > a ridiculous ommission. > > If the section in the documentation titled 'File Locations' isn't the > appropriate place to document the locations of the config files, then I > don't know where the hell is. > > > ​The "installation instructions" covers where files are placed when installing from source. > > https://www.postgresql.org/docs/10/static/install-procedure.html > > If you are not installing from source them whomever compiled the package you are > installing will have specified where they are placing files and you will need to > inquire of them. > > The PostgreSQL docs don't cover file locations in depth because each of the many > platforms we support have their own conventions. It is of course possible to obtain the current values contained by the settings listed on that page with e.g.: SHOW config_file or SELECT setting FROM pg_settings WHERE name = 'config_file' Server has to be running, of course. The various ways of getting current parameter values are documented on the previous manual page here: https://www.postgresql.org/docs/10/static/config-setting.html#config-setting-sql-command-interaction Regards Ian Barwick -- Ian Barwick http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs