Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wVEMa-001nwy-0m for pgsql-admin@arkaria.postgresql.org; Thu, 04 Jun 2026 20:08:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wVEMY-008SqZ-2t for pgsql-admin@arkaria.postgresql.org; Thu, 04 Jun 2026 20:08:22 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wVEMY-008SqR-1h for pgsql-admin@lists.postgresql.org; Thu, 04 Jun 2026 20:08:22 +0000 Received: from mx3.edn2.eu ([49.13.39.158]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wVEMV-000000017mv-4A80 for pgsql-admin@lists.postgresql.org; Thu, 04 Jun 2026 20:08:21 +0000 Received: from smtpclient.apple (p200300fb4f0749016d2a2818977614e7.dip0.t-ipconnect.de [IPv6:2003:fb:4f07:4901:6d2a:2818:9776:14e7]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx3.edn2.eu (Postfix) with ESMTPSA id 4gWbGl6XYBzkHK for ; Thu, 04 Jun 2026 22:08:15 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ellael.org; s=dkim; t=1780603696; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=RyldhrQNdD2TVBwaUDvEHKgPkI94kzVV55ofNwbQiTw=; b=LHyMUN1Vb7DfpfSFw84TQxRQ982DcBU3PiBtQywcig9vmbhJqhd+LdG108mYwSrm8KDIBC AdYl1uWf9rovXJrwCN8nuMndjZTToPkr1Pj0Pvovu7Dzwg6WxIMx+GwZ/ccMqhluYg/65k OZ+IUUIKNYan5pDokIs20Tq4BkI9fYH11z34JK8Na3NDYAsy9Y+igYQrPnTcLUKwK+UolZ dZ0P+bBijOCTOm9hwVige6jnlE6uJ7J/NhEZJkNcy9W6rt4HowOol2L2h0GZgywi3qbcFZ TjG5neCKSeU7iPhhp6xM07SOHEZ1y5Gu/T/PjROZ2teqErEv4JIKT1dl2P4SbQ== From: Michael Grimm Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.600.51.1.1\)) Subject: Re: Howto tell pg_ctl to use a non-default directory for config files Date: Thu, 4 Jun 2026 22:08:05 +0200 References: <3441657.1780603341@sss.pgh.pa.us> To: pgsql-admin@lists.postgresql.org In-Reply-To: <3441657.1780603341@sss.pgh.pa.us> Message-Id: <41D74517-751E-47F2-9BA7-FE3E574C2FAE@ellael.org> X-Mailer: Apple Mail (2.3864.600.51.1.1) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Tom Lane wrote: >=20 > Michael Grimm writes: >> Question:=20 >> Is there a way to tell PostgreSQL to look for config files in e.g. = /usr/local/etc/postgres, where normally all config files reside in = FreeBSD? [2] >=20 > Typically you would say "pg_ctl -D /usr/local/etc/postgres" to point > it at the config file. Then you would need the config file to include > data_directory and perhaps other settings pointing to wherever the > actual data files are. See >=20 > = https://www.postgresql.org/docs/current/runtime-config-file-locations.html= Ah! That's what I failed to find in the documentation :-( Thanks and regards, Michael