Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nSFMc-00042p-OT for pgsql-admin@arkaria.postgresql.org; Thu, 10 Mar 2022 09:45:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nSFLc-0002mv-QK for pgsql-admin@arkaria.postgresql.org; Thu, 10 Mar 2022 09:44:40 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nSFLc-0002mm-Bu for pgsql-admin@lists.postgresql.org; Thu, 10 Mar 2022 09:44:40 +0000 Received: from mail-ej1-x634.google.com ([2a00:1450:4864:20::634]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nSFLZ-00079D-JE for pgsql-admin@lists.postgresql.org; Thu, 10 Mar 2022 09:44:39 +0000 Received: by mail-ej1-x634.google.com with SMTP id hw13so10353605ejc.9 for ; Thu, 10 Mar 2022 01:44:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20210112.gappssmtp.com; s=20210112; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=E3DQkAHBMz6GNxJWiDLJI41zy4FrBXRUH47ZXatJun0=; b=5f1XrDnBSKFDUNs0Ok7kHZIgzcHuvlltXC8WUkKAJt++rqfIC0gnd+7ltniqcLJq6M Kd0v2AxeAZa5emjt9YIUkbWOilSK+9/jFzMGYK1OpnPuyMmt+FNX7LDeuoMX7ACmjhZA fjS6BKwT7yOfog1ZP1P19JCEK/2+UTv6aM2h7ECd7BHqlwkOkocMnZtFDA5QksBWin4V jKoHKgYwjFHaqZBKCHXJw6eRSQb0k0aDYQJX1hBABOoMx9SHHdxzpkIoPoVRDhwVO0Wn Dc4CXazCs+lBmFzWgiARTti/+h6UWWvc7F+o8QuG//VyOlJ1vdiulUlkm4gn/0WS4LBx jTkA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=E3DQkAHBMz6GNxJWiDLJI41zy4FrBXRUH47ZXatJun0=; b=uqYt7eJKcnMhO+fq2d5LpOVYUumgMOBUAo/J3DME36kmX078gCJJWTAjBydDXG1Ufi UJBpaLxXxO+jES7R7OHsqbMSO5Pv/d8aREJ9Te3LfgI16y1S5n0QfNKFKLAFURcunTF4 IKbsw8rtHlPG7IrP8qbCdteNAZXjivLIMx8Yv7kGOTQyQkGXtQCJDG/osFV+uSloHlJu ZoyDYxx083nFAkcJOb/GJVisuzPXLFlr3NcYhkggmG9pFsYYQ5lLl4BYexPiENbZ7HqA /ZxLc0EQWTYYwphX7to/cF7u4op9uTbD5R1n7w72c6WSXSLDfQFUt8BmcXFvK2+mQ8I9 96kg== X-Gm-Message-State: AOAM533O1nzQ/OupmDEZEeXepw0pci6wDZ+7MJHKm3PpKlHf3Gqygewp yXdXoeAcXcTKTIHZRxihrhiZMA== X-Google-Smtp-Source: ABdhPJyDvellQPdcJUh+FD8Y1tzObMXu/D8oeEH65I8g/E17r370v/U3RHW8efuhGUnGBCWxsBboZQ== X-Received: by 2002:a17:906:7751:b0:6ce:e3c:81a6 with SMTP id o17-20020a170906775100b006ce0e3c81a6mr3311221ejn.278.1646905474131; Thu, 10 Mar 2022 01:44:34 -0800 (PST) Received: from localhost.localdomain ([2001:871:5e:8017:c3e3:464a:47e2:18d4]) by smtp.gmail.com with ESMTPSA id a1-20020a1709063e8100b006ce06ed8aa7sm1601471ejj.142.2022.03.10.01.44.33 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 10 Mar 2022 01:44:33 -0800 (PST) Message-ID: <8aefabdcee722979c2b01ef103e2835b2e27629e.camel@cybertec.at> Subject: Re: PostgreSQL Installation From: Laurenz Albe To: edi mari , pgsql-admin@lists.postgresql.org Date: Thu, 10 Mar 2022 10:44:32 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.40.4 (3.40.4-3.fc34) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, 2022-03-10 at 10:04 +0200, edi mari wrote: > What right way to split the PostgreSQL data between the file system (mount point) in Linux in the installation process? Create your own file system for the data directory, so that PostgreSQL cannot fill the root file system. It can make sense to provide additional file systems for "pg_wal" and the log files. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com