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 1oIsdo-0000Px-Rp for pgsql-docs@arkaria.postgresql.org; Tue, 02 Aug 2022 14:13:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oIsdn-00007I-5E for pgsql-docs@arkaria.postgresql.org; Tue, 02 Aug 2022 14:12:59 +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 1oIsdl-00005J-NM for pgsql-docs@lists.postgresql.org; Tue, 02 Aug 2022 14:12:58 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oIsdi-0001w9-I7 for pgsql-docs@lists.postgresql.org; Tue, 02 Aug 2022 14:12:56 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id D11C95C010A; Tue, 2 Aug 2022 10:12:52 -0400 (EDT) Received: from imap49 ([10.202.2.99]) by compute2.internal (MEProxy); Tue, 02 Aug 2022 10:12:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eulerto.com; h= cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm3; t=1659449572; x=1659535972; bh=qoy4wk0ovc V3s/IcWU8evScJv3AMQ8sCKpZr2xUx+Pw=; b=b0e0YyNcuElIML8PPtD8qOtSAv y6928hn0L/ET5RwHHiblLv8oxJmdE3ZAyMVCJFCfXoYXFfSIX/PJWO3b4lv9W8Us BRTrMSZJV/87YkORXDQMG597EQEklr5yOY45b5bMSM1pIFriPIXuQzuxZ8f+0iYY TnXIib3F92UnbqyT77MCG0gVKvS6XYukN0s+iULMnfOrcbDeLMA/wuz33QPzuSaJ 2FkKQFm29mSQVX+zpYt99ylvEi2/ewnmCvrgxIkIzKHI7SFX1UTqmQ7G5STie+8d ky50Zyvg62q4ichl5wjyCft0Ud1UjBpY6czffzHoDUmXmH3XQ+oErsS0LbCA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; t=1659449572; x=1659535972; bh=qoy4wk0ovcV3s/IcWU8evScJv3AM Q8sCKpZr2xUx+Pw=; b=i+AJLroS5JbfQGGC3ZTT2BafrcWNmdXQFGyIBWD673pA i4Ynd4ORa0rRnzev9ZASHMU7J2jeErr3vr9CER+UfVT+6EjbMRmo49x516wD7y9e N75xlLoRk2p1X5U7gyqRCoHHy3H7fYkkdWgwNbEKA64gtVoeLEqGOS7VEXUqYcYy cXQ6WuDQJexVORI9ToT9aFtoXTmI9EbYnq4EMQD7pk26RKmeUNS7iek+8/rZ+9zN zzbfc7E8bXAAG53Ctn5evYzURHeYfH9D6XLwWcxlEO0mX4++jdm7C+scNRwujhld CaZ8/xK3IvMlT3osuST1+GGgYfbVI7YM6vGmbeMfeg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrvddvhedgjeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsegrtd erreerreejnecuhfhrohhmpedfgfhulhgvrhcuvfgrvhgvihhrrgdfuceovghulhgvrhes vghulhgvrhhtohdrtghomheqnecuggftrfgrthhtvghrnhepueetiefffeekhffgvedufe eijeevveeugfduleejteekhedttdetleegkefgtdetnecuffhomhgrihhnpehpohhsthhg rhgvshhqlhdrohhrghdpmhhitghrohhsohhfthdrtghomhdpvghnthgvrhhprhhishgvug gsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhho mhepvghulhgvrhesvghulhgvrhhtohdrtghomh X-ME-Proxy: Feedback-ID: i0c21471d:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id E4F6515A008B; Tue, 2 Aug 2022 10:12:51 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.7.0-alpha0-758-ge0d20a54e1-fm-20220729.001-ge0d20a54 Mime-Version: 1.0 Message-Id: In-Reply-To: <360f5fd7.46a.1822e5e2eaf.Coremail.msdnchina@163.com> References: <360f5fd7.46a.1822e5e2eaf.Coremail.msdnchina@163.com> Date: Tue, 02 Aug 2022 11:12:31 -0300 From: "Euler Taveira" To: "yanliang lei" , "pgsql-docs@lists.postgresql.org" Subject: =?UTF-8?Q?Re:_pg_document_is_not__recorded=EF=BC=9Amaintenance=5Fwork=5F?= =?UTF-8?Q?mem_can_not_large_than_2GB_in_windows?= Content-Type: multipart/alternative; boundary=f8d1af111aeb4c74bd5e20929b4f5687 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --f8d1af111aeb4c74bd5e20929b4f5687 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable On Sun, Jul 24, 2022, at 1:01 AM, yanliang lei wrote: > pg document is not recorded=EF=BC=9Amaintenance_work_mem can not larg= e than 2GB in windows=E3=80=82 >=20 > https://www.postgresql.org/docs/14/runtime-config-resource.html >=20 >=20 >=20 > I suggest that=EF=BC=9Amodify maintenance_work_mem parameter descripti= on in the pg documents=EF=BC=9A >=20 > add maintenance_work_mem parameter size limit in windows platform >=20 >=20 >=20 > if you set maintenance_work_mem large that 2GB in windows platform >=20 > postgresql service can not start=E3=80=82=20 >=20 > in the windows event viewer =EF=BC=8Cthare is the following error: >=20 > "ERROR: 3072000 is outside the valid range for parameter "maintenance_= work_mem" (64 .. 2097151) >=20 >=20 >=20 > and the work_mem parameter also has similar problems as above=E3=80=82 >=20 > https://www.postgresql.org/message-id/17895.1315869622@sss.pgh.pa.us >=20 I don't think it is a good practice to document operating system limitat= ions because these limitations may be resolved in later versions of the opera= ting system. In this case, an OS choice (int and long are 32-bit values on 64= -bit Windows) imposes a Postgres limitation. The documentation does not menti= on an upper limit and it also provides a suitable error message. Both are suff= icient to provide proper functioning for Postgres. IMO that's a change that som= eone might be excited to address in the future. [1] https://docs.microsoft.com/en-us/cpp/build/common-visual-cpp-64-bit-= migration-issues?view=3Dmsvc-170 -- Euler Taveira EDB https://www.enterprisedb.com/ --f8d1af111aeb4c74bd5e20929b4f5687 Content-Type: text/html;charset=utf-8 Content-Transfer-Encoding: quoted-printable
On Sun, Jul 24,= 2022, at 1:01 AM, yanliang lei wrote:

pg document is not  reco= rded=EF=BC=9Amaintenance_work_mem can not large than 2GB in windows=E3=80= =82

https://www.postgresql.org/docs/14/runtime-config-res= ource.html


I suggest that=EF=BC=9Amodify = maintenance_work_mem parameter description in the pg documents=EF=BC=9A<= br>

add maintenance_work_mem parameter size limit in windows = platform


if you set maintenance_work_mem = large that 2GB in windows platform

postgresql service can= not start=E3=80=82 

in the windows event viewer =EF= =BC=8Cthare is the following error:

"ERROR: 3072000 is ou= tside the valid range for parameter "maintenance_work_mem" (64 .. 209715= 1)


and the work_mem parameter also has si= milar problems as above=E3=80=82

https://www.postgresql.o= rg/message-id/17895.1315869622@sss.pgh.pa.us

<= div>I don't think it is a good practice to document operating system lim= itations
because these limitations may be resolved in late= r versions of the operating
system. In this case, an OS ch= oice (int and long are 32-bit values on 64-bit
Windows) im= poses a Postgres limitation. The documentation does not mention an
upper limit and it also provides a suitable error message. Both= are sufficient
to provide proper functioning for Postgres= . IMO that's a change that someone
might be excited to add= ress in the future.




--
Euler Taveira
EDB   https://www.enterprisedb.com/

=
--f8d1af111aeb4c74bd5e20929b4f5687--