Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dKsaY-0006Uk-Bm for pgsql-performance@arkaria.postgresql.org; Tue, 13 Jun 2017 20:38:58 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dKsaX-0003Fy-UU for pgsql-performance@arkaria.postgresql.org; Tue, 13 Jun 2017 20:38:57 +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 1dKsaW-0003EN-Kw for pgsql-performance@postgresql.org; Tue, 13 Jun 2017 20:38:56 +0000 Received: from mail-yw0-x234.google.com ([2607:f8b0:4002:c05::234]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dKsaT-0003fI-TZ for pgsql-performance@postgresql.org; Tue, 13 Jun 2017 20:38:55 +0000 Received: by mail-yw0-x234.google.com with SMTP id 63so57337435ywr.0 for ; Tue, 13 Jun 2017 13:38:53 -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=qZFVvVsZGR46NygeoV0Puy2l8GOxWk41OyH3J1USFCU=; b=hvxmvky0PAjBART/AWAVASATtYJH3ds1u54Hq49jF8BdTDw+xnQ2umHyYKKRvDHVn9 YppfUE9wKhQbfg/TIqnjp8kStQpGibtRNH/8wTQ/AIiwrGu0UM02dWGMm1rzlyd2sthD szqUXRcYwplqx981QoPI7tZtOlPEY+A8CJZfN26sQXSCFBYIdAF6RhXVhrbcLDX0PQIV Xx2IFysiKEAcQYx/K6P+roQhllTWZYKP9rPD2e/mpRKD3TqfoLL+bGG6piHAmswYE9fD JxubUVOE9gdTN4GP5n/pK3xhboxQgs7efkvbEY7dFRVwI7+DeV9XNYRLRE9ug6Lmfo2l OxwQ== 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=qZFVvVsZGR46NygeoV0Puy2l8GOxWk41OyH3J1USFCU=; b=AT+yVu1UOvg5oX2JLb5vON4vIVY08w0skg0K8ZGyYmrnMiKfLUr8s5VtcVzBEsfJlA rgDqTsXjCZgjIVcdeHdkMdjQq9CwiddQc0KArh0QXNihhy2697Bg1FgUhlqrmcw8t8gW bS2e9IX/VBWthcFON9hpeNWzLu+688aQQBOXV4dtc4bOSUVwwg0dHGSytqfQ0+jjYO+T q5238TxumBPkBhXzxgqH43+N+81Kh1hYf7BMaWGnnXlZ4ZSzHGj1Zpo8frHd+xP1+9Ep TVl7VNdbbuSUTLn9JN9I6VUibNPKB3CRUc/4IeSf5JDw73TkYp24WCLb1zJig+oICJEh 1bBA== X-Gm-Message-State: AKS2vOwr7dzSSOt0OaB1K3pwF+8YMAOxOeWwOjeDRkuJRXBJHQ0d2Cad s+atNvXte4kUTh8zNs3QGF2JklKVyg== X-Received: by 10.129.197.65 with SMTP id o1mr4601987ywj.261.1497386333308; Tue, 13 Jun 2017 13:38:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.198.77 with HTTP; Tue, 13 Jun 2017 13:38:52 -0700 (PDT) In-Reply-To: References: From: Michael Paquier Date: Wed, 14 Jun 2017 05:38:52 +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" , 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 10:39 PM, Cocco Gianfranco wrote: > ./configure --with-wal-segsize=1024 > > checking for WAL segment size... configure: error: Invalid WAL segment size. > Allowed values are 1,2,4,8,16,32,64. > > Please, how can I do? When trying to compile Postgres 9.6, the maximum value is 64. If you want to allow 1GB of WAL segment size you will need to wait for 10, or just use 64MB. -- Michael -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance