Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dKT8y-0003O1-5u for pgsql-bugs@arkaria.postgresql.org; Mon, 12 Jun 2017 17:28:48 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dKT8x-0002Bj-Ob for pgsql-bugs@arkaria.postgresql.org; Mon, 12 Jun 2017 17:28:47 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dKT8F-0008Cm-4O; Mon, 12 Jun 2017 17:28:03 +0000 Received: from mail-ua0-x22f.google.com ([2607:f8b0:400c:c08::22f]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dKT8C-0004ys-9a; Mon, 12 Jun 2017 17:28:02 +0000 Received: by mail-ua0-x22f.google.com with SMTP id 68so43020827uas.0; Mon, 12 Jun 2017 10:28:00 -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=320RYWlCgX23Go3i1UqifYNc15LiEvkhT9IFSEZoDXQ=; b=k0jt8Li8GRXF6T/8PV0KYUXY5HNBhFgd6TnSWlw6s4V3jQaJ70tJX3F4HO3fqy8dGn 1SJl1TG6oEk/gO8/hnW5V+EatBW7c7UdZVHVGURxhRhluaPP03luhz3WsABgrj5sqNc5 768DGRh855dRykCY7IBLYtjcO6o4huPHifRxLDVDTnR6tb49k5/gtaBzSjvdzJvsZDRp RDTG2JBXKilYUuLTN8Vwip7yDZc3KkglNVpC3DBS8alIGGNGU/7i14GtLNyx1TDGpwI9 uZGN+dAct4DgYmBuugBO63ULWwNrTNo/DO5R42DWm0adJ3xA9ei1cbmjOLwReTR6HTaH DIrw== 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=320RYWlCgX23Go3i1UqifYNc15LiEvkhT9IFSEZoDXQ=; b=q+4GI7LiY4z4G2rlecyW6LV3nEocYm+EZvMq3n02ete5mhYpmjRipYu8ivl7MRaYmr lcfCO76WUWEBa8sYFlgCVQQwMtagzhxq1NiXNetrW9tVwAwvZeL8DR3Jq26AXfXvFUIr d+AAE9jlYlkYFS9mMfNYUXoMg+hH1bpVz7LU+QwQZj6TQEvks4H1SqQtiPWJL3edZESb x11g1f6Zx1TloIXWANIw89dPcDdPmchTzfkPlUxr/iAB96fK/8x0Bf6XQ0mEq0iIlP0l u48atNmMvslLnX9CFtC/1Wzmdlnmi6pxqncosaWigymD4cznQdimcvw79pvbq1zKO6FT 6t8Q== X-Gm-Message-State: AKS2vOwMysnCBMGxodQQH43V09qNI1chNysurRh234wcswFYLngy8fgt 2TxQgVzai4TMr2OZwajY0UJfdnfK+g== X-Received: by 10.176.79.227 with SMTP id t35mr32299uah.5.1497288478934; Mon, 12 Jun 2017 10:27:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.159.39.166 with HTTP; Mon, 12 Jun 2017 10:27:58 -0700 (PDT) In-Reply-To: References: From: Jeff Janes Date: Mon, 12 Jun 2017 10:27:58 -0700 Message-ID: Subject: Re: Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64 To: Michael Paquier Cc: Cocco Gianfranco , "pgsql-performance@postgresql.org" , "pgsql-bugs@postgresql.org" , DBA Content-Type: multipart/alternative; boundary="f40304364386e9cc650551c6a3b5" List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-bugs Precedence: bulk Sender: pgsql-bugs-owner@postgresql.org --f40304364386e9cc650551c6a3b5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Jun 9, 2017 at 3:43 PM, Michael Paquier wrote: > On Fri, Jun 9, 2017 at 10:55 PM, Cocco Gianfranco > wrote: > > Is there a way to fix =E2=80=9Cwal_segsize=E2=80=9D to about 1 Gb in 9.= 2. version, and > =E2=80=9Crebuild=E2=80=9D postgreSQL server? > > As long as you are able to compile your own version of Postgres and > your distribution does not allow that, there is nothing preventing you > to do so. > But there is something preventing it. wal_segsize cannot exceed 64MB in 9.2. v10 will be the first version which will allow sizes above 64MB. Cheers, Jeff --f40304364386e9cc650551c6a3b5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On F= ri, Jun 9, 2017 at 3:43 PM, Michael Paquier <michael.paquier@gma= il.com> wrote:
On Fri, Jun 9, 2017 at 10:55 PM, Cocco Gianfranco
<Gianfranco.Cocco@eng.it&= gt; wrote:
> Is there a way to fix =E2=80=9Cwal_segsize=E2=80=9D to about 1 Gb in 9= .2. version, and =E2=80=9Crebuild=E2=80=9D postgreSQL server?

As long as you are able to compile your own version of Postgres and<= br> your distribution does not allow that, there is nothing preventing you
to do so.

But there is something preven= ting it. =C2=A0wal_segsize cannot exceed 64MB in 9.2. v10 will be the first= version which will allow sizes above 64MB.

Cheers= ,

Jeff
--f40304364386e9cc650551c6a3b5--