Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dKiDW-0006Yx-HS for pgsql-performance@arkaria.postgresql.org; Tue, 13 Jun 2017 09:34:30 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dKiDV-0002eD-R2 for pgsql-performance@arkaria.postgresql.org; Tue, 13 Jun 2017 09:34:29 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dKiDU-0002dF-OD; Tue, 13 Jun 2017 09:34:28 +0000 Received: from mail-yb0-x22a.google.com ([2607:f8b0:4002:c09::22a]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dKiDO-0007V9-0x; Tue, 13 Jun 2017 09:34:27 +0000 Received: by mail-yb0-x22a.google.com with SMTP id t7so5602330yba.3; Tue, 13 Jun 2017 02:34:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=vF2nJChHEGtcxYQWO73uytR5ptQdj/Pd1jpdch+iMy8=; b=qc+nlZERHUJYes5jjOiT305nq5UFJUCeEn2ExT5OzMjJ6q5lei6PQw5wEA94WlcmTB wyseIcbz1piA3Yni/N7dSxLbNY21ItNQj9BFxR/VyOgU8SQoLP/5tW3p/eZ2oNall87B geWe/QCNyVRm9z5c3rjlDl80MQSqTdtp4P75hGc7iVc/kexBzA0zQhPBx6A5CNSrQEKU 7nlN94+XuGvVHOBNR7HwmTY1oPomGwupU7132pElvhy44IjLmGOBHvVC7E8CzrZ6BMrH a/Isfg3+PWPvboOiUg39JaOkoa1EL/nm7/cUrCA2ruhI1vVqt7cTVeWA+m807DKJ5jgj QLRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=vF2nJChHEGtcxYQWO73uytR5ptQdj/Pd1jpdch+iMy8=; b=gB0BOgchJSMQZ9qqrjiQIv1TEqme2kW5FjmUJAUz64WK6iw0CS/0+xIa2lIZjYyoHl t3VLHgfZp+uqj+foycPvx+PAhYKjqz1XvKG9FibTetHVSTQsL+EUAzcQFbBjQfrytDVy NAxqrn5QLRfDYqOpYWM2y/YJ9cqiIepu3vZfIj++iuVL51WNeIRwzGejd9wo5Z1DLqDG XaCbMvg7Jpjhq1vRQKUbociJC56c+CPcFsfn2a5vNfYI1rr3cD0r02IuBqIOFtL2ziug xho/G215uZ1LIVEDKtuhOIruGyda1gAmMG6HEGOWiHbEmo6iyrjKOqP0GKUat2Vjn7Qt xOYg== X-Gm-Message-State: AKS2vOxUusRR2jp37XFzqYspmKzItzYlEL6/p2MvP51VVX42uoE7s/5q QyFpqYwtLq0svqxP78swCarh6MMeRQ== X-Received: by 10.37.111.194 with SMTP id k185mr2341807ybc.116.1497346461112; Tue, 13 Jun 2017 02:34:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.198.77 with HTTP; Tue, 13 Jun 2017 02:34:20 -0700 (PDT) In-Reply-To: References: From: Michael Paquier Date: Tue, 13 Jun 2017 18:34:20 +0900 Message-ID: Subject: Re: [BUGS] Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 To: Cocco Gianfranco Cc: Jeff Janes , "pgsql-performance@postgresql.org" , "pgsql-bugs@postgresql.org" , DBA Content-Type: text/plain; charset="UTF-8" List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org On Tue, Jun 13, 2017 at 6:10 PM, Cocco Gianfranco wrote: > If I understand it well, we can build a new postgreSQL server, by setting > this value into "configure" file? > > --with-wal-segsize=SEGSIZE becomes --with-wal-segsize=1024 ?? Yes, but as Jeff has pointed out upthread, this value can just go up to 64 when using 9.5. -- Michael -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance