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 1kpFcn-0001fc-NT for pgsql-admin@arkaria.postgresql.org; Tue, 15 Dec 2020 19:04: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 1kpFcE-0006BW-UC for pgsql-admin@arkaria.postgresql.org; Tue, 15 Dec 2020 19:04:06 +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 1kpFcE-0006BP-Hk for pgsql-admin@lists.postgresql.org; Tue, 15 Dec 2020 19:04:06 +0000 Received: from mail-ej1-x633.google.com ([2a00:1450:4864:20::633]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kpFcB-0000eJ-Ke for pgsql-admin@lists.postgresql.org; Tue, 15 Dec 2020 19:04:05 +0000 Received: by mail-ej1-x633.google.com with SMTP id j22so11270650eja.13 for ; Tue, 15 Dec 2020 11:04:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=nZKqBgsVs/H52vSXOg3td0l5reuc4ve4XwOCk1rumdA=; b=KY+ME/M4TegvYbN2p3mJrM4kMRb7YFLfuDrH7W2bHyn061/1V7Qac8NzeRbwZfAedh no2vbQUa+2DrT4Nh8igNfBkSOID3ZdSRcoMyN4E1lTPAM+8N02C+BvfzWIhMMF9/5rEu 3BmfKeV+/evJh3+mu4J6QkxzMVCkVH5SGMdyBZuHUYXZKiyNaVi85OcULAk3RSMjtjwh mBSa+MwODnDJMk5LkzPCyGr7egPzN3hfyNyMzquWNzb6lcbciWhR1o3lsW2SJ/sRmhM1 SJZrdJW3cxQVQlrqQqtevU45Yrn/42JTAG2rJ76HdjTqcRJvKhjdqmUilnNDG7tp61PM wW+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=nZKqBgsVs/H52vSXOg3td0l5reuc4ve4XwOCk1rumdA=; b=mEoquGhapjl7jDI6gpJAnESSb0sE/WMQJQRgaCdqe1TjLm8QdTvYKwfkVJZgNGs+qy K5ycJW0hqmm6r/nc6DxIyMgr3SCqdJwZeahPVlfdJHuHG/wrK01A9BFi/gbU0ZmBi1Hi wi89aekOnGJmzH7yEr4P/vjLuFll4Vq3LcjQW2/Kg+K2zW4CQne2Os5tczz7Fu8bpzTE 7j+4S9lnl47zDGBtJo4CZ13ttZd/Td+oO3XWitjzV2YFrxWzn9883bWCUT0Bg5kInR0o IEolEreyl0u3SLpUOCzRazpAmu0x46dgLUuv/mcnF+3PITIDztP1L3hWCTL/g17vNHyQ oOmg== X-Gm-Message-State: AOAM5332aYkTTpHM+MJTuV/qFdbO3VxVKgMig85GYogJTMxWZayJqZ59 pZ4laS186zDTocNCB48NHJ3AkQ== X-Google-Smtp-Source: ABdhPJw22c+kZ73xtSWFuPVzsg3c6mz/nb9tBDtDaYPBHA+rup3SHjHWHXicj699njpKKuwlGryTgQ== X-Received: by 2002:a17:906:fa8b:: with SMTP id lt11mr6106352ejb.94.1608059041076; Tue, 15 Dec 2020 11:04:01 -0800 (PST) Received: from localhost.localdomain (217-149-170-124.nat.highway.telekom.at. [217.149.170.124]) by smtp.gmail.com with ESMTPSA id u19sm2134333ejg.16.2020.12.15.11.04.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 15 Dec 2020 11:04:00 -0800 (PST) Message-ID: <250003f95a8fa8c18a070989a26b4b366cd13dff.camel@cybertec.at> Subject: Re: Create Cluster --- Change the Block Size From: Laurenz Albe To: Ankush Chawla , pgsql-admin@lists.postgresql.org Date: Tue, 15 Dec 2020 20:03:59 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-1.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Tue, 2020-12-15 at 23:05 +0530, Ankush Chawla wrote: > how to change the block size while creating the cluster You cannot change the data file block size (8kB) during "initdb". You'd have to recompile PostgreSQL for that and use --with-blocksize=BLOCKSIZE with "configure". I recommend not to do that. But you can use --wal-segsize to set the WAL segment size during "initdb". Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com