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.94.2) (envelope-from ) id 1u8rns-00CpKQ-NO for pgsql-general@arkaria.postgresql.org; Sun, 27 Apr 2025 02:31:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1u8rnp-008RmB-4f for pgsql-general@arkaria.postgresql.org; Sun, 27 Apr 2025 02:31:33 +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.94.2) (envelope-from ) id 1u8rno-008Rm2-OG for pgsql-general@lists.postgresql.org; Sun, 27 Apr 2025 02:31:33 +0000 Received: from mail-io1-xd42.google.com ([2607:f8b0:4864:20::d42]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1u8rnn-0029MV-0Y for pgsql-general@lists.postgresql.org; Sun, 27 Apr 2025 02:31:32 +0000 Received: by mail-io1-xd42.google.com with SMTP id ca18e2360f4ac-86192b64d0bso327007039f.3 for ; Sat, 26 Apr 2025 19:31:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1745721090; x=1746325890; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=z2N3RvZi+1m8BmS4HitmHaXk/6px6E+jUXN5pfnZ4Jw=; b=l8p55155ehpO56apTr3IshMVzdF23/tVamt1J9bN55rxfKEIWh4pwikdzbqv5o2jB8 h5xJXZAvKNqhPbMXyHsZZwDkbOIC2qAg3lar7Y0npXTW/hUu2emGcQNRvXsGLC378/hT Y8i9k48pD1adux67BRtZCuslL3gdgSDZnepxAWRSNCgPW0gKMytz8J+bUXG5lckOE1Nu PioN2ZINo4ky1RqyEA7V/YrEF2ssL/1KM1/U6zLsl8pwwo9tdjBvi4PW7WaAv+LLkPrt d55Tgc+r3vfwCetu/IK7GAb7fxWyr4KycBtJf+OILeZKlZXIuYMpL6wTN1Q/KN35xldz RD5g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1745721090; x=1746325890; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=z2N3RvZi+1m8BmS4HitmHaXk/6px6E+jUXN5pfnZ4Jw=; b=mT28OM6OksuKpDAkALKoa7DCQsWOLT52XFzn7zpeMAnXypA7mEKNlM6O2ehxGXs4O+ e7WOlu2AJu8p3nEqRR7JUVER+yugJXQG2yK3Gyf8j1MT3e2qOul0plq0poAOBWbowKz+ ehi65qI/vIeWzQhVzdBgmfoWvv8PXi+daPVNW+Wa6KSnWs/A7TS6Kzzb54Kh0mxgbzNU d4tut3zX+t3klrXfH4wVPGxQ9zYy4itGEMU5irqzDcGMEfZqfsU4711hyh+IeOXEtCiY FjWxBaXuQlPHhAskLmC9bXkTuU8z12Afq4sfBZNnb7KkYRwRFMkSwfyQgxQGnbIyeh87 ZJGg== X-Gm-Message-State: AOJu0Yx8zxMJIkJqFMrMxf+zPJ7kbTPy/9QYQpCxN1dKJNhTv6GMuyjO S1Ok/4wPYUV0ZRGoG1qbtaf+HarQWYd7eFrqdg5bb12dyIW0lykai0239epHd1pVYeKYGDKnx+u aeSLJUeC0Of4CcnLnbL6qFsUWa2g4tqz50AM= X-Gm-Gg: ASbGncvsGX2DnKBehtW/tyyLj1Ax1RN/iHtObMKos0mcrNeOO6qSUumBF7iTAg5pPhZ MNGzivQjeBq2AV8qstiF2DixsP24aoMn8x+HXimYwSWILtWrS5Nc/b4PF8cndB6LOvoPA66IR1l /EYqXRsdNCT/gLJLreiX7rKiU= X-Google-Smtp-Source: AGHT+IFGJXAS8wSg4DnmzuISi3a9vOr52yRA6GeH1LrdxX6l1cqpm+VONCJ/Zl/PjMnOaXk4w4FC+FKT6RP/NyLdSAw= X-Received: by 2002:a05:6602:1514:b0:864:48d3:a5cf with SMTP id ca18e2360f4ac-8645cd88569mr925962539f.12.1745721090254; Sat, 26 Apr 2025 19:31:30 -0700 (PDT) MIME-Version: 1.0 From: Marcelo Fernandes Date: Sun, 27 Apr 2025 14:31:19 +1200 X-Gm-Features: ATxdqUGr3kOa9FoegbOUY1zyjMKqPQlAtG0coQzK4AkPSsstQJ5cgdRKPlCERz0 Message-ID: Subject: Changing default fillfactor for the whole database To: pgsql-general@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi there, I have a scenario where virtually all user tables in the database will need to have a lower fill factor. It would have been handy to have a way to set this default, but as of now, I don't think the default can be changed. I have looked at `share/postgresql.conf.sample` file, and couldn't see anything indicating this value could be changed. Though I'm aware there's an ALTER TABLE command that can be used for that, I think it would be good to avoid some future errors (forgetting to set it) if I could change the default value. Does this make sense? Have I missed something about being able to change this on a database level? Thanks, Marcelo.