Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1i5Wlc-0003W1-D9 for pgsql-docs@arkaria.postgresql.org; Wed, 04 Sep 2019 15:00:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1i5Wlb-0002dg-8g for pgsql-docs@arkaria.postgresql.org; Wed, 04 Sep 2019 15:00:15 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1i5Wlb-0002dZ-1d for pgsql-docs@lists.postgresql.org; Wed, 04 Sep 2019 15:00:15 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1i5WlY-0005eq-Mu for pgsql-docs@lists.postgresql.org; Wed, 04 Sep 2019 15:00:14 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 85FF3706; Wed, 4 Sep 2019 11:00:09 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Wed, 04 Sep 2019 11:00:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm2; bh=N4TYm2eG3Oev90cBh9RBqzZZK3l JBSMPbX0hPcpBnZE=; b=TJ8dHIZrJTVdDA1OUdmWxpy72lmRM6PbbZBZ13hoXvJ 0kW88hC81Hrhg7GwCTRkNu1LGhL8WaDkTvkhQk6a5L/g21iYRUGtepXOtL0gkNwd zUtR8VN1x1iHBs2AG4cXiCmZEXYKa/6ASUGV6EaBQhxSgM/SsfohZGB7kPiWn64U m8Z7EqWsQs4DzsIxyXXUOHQVV13GHuqCyq9I31/mLoC71FBSIUvd6bLJgsLMOfmX KoQAH+7UFLDFY/B6kkB47VwZzIWCipB5ciZJew+M7AnE3i3AbOANScejA+Wj05El +erkkLWFSTL0ApniJ5CvUEblkSsMcV+JCwqcrhv9ESA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=N4TYm2 eG3Oev90cBh9RBqzZZK3lJBSMPbX0hPcpBnZE=; b=u6Eqs03xPxI99GbcGAz4iU JK4wHE3P0eBVSts48O9CU0U2U3HCPF6XaxJi2FbddcEIl6kETL5/j7blQyHrFisx Sf84FYL8S9uvQ4CHfpoRdxB3UTU7cEuK/zzWsme1OHKKQetO5VTulX8xsafMDGjt ki4hHAY/e7eILGDniRyvlNucXCdNco5Cq0a0pup/IwlgDKZrSODV355yrxdW2s72 NE3SGhhVMfD4J5u071OhhdSWhE3so1fPds2tjX6kWCb4cp7FT/y5shVVmc2UEP1a kGHCMRRQb3aG26yVv7JDjobWzQ1Dnq2rQISltoU843vuQkUmteKoQ9zgDfExlxDQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrudejhedgkeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpeetnhgurhgv shcuhfhrvghunhguuceorghnughrvghssegrnhgrrhgriigvlhdruggvqeenucfkphepke ejrdduvdefrdduleekrddvtdejnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrnhgurhgv shesrghnrghrrgiivghlrdguvgenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from intern.anarazel.de (i577bc6cf.versanet.de [87.123.198.207]) by mail.messagingengine.com (Postfix) with ESMTPA id A6F5580083; Wed, 4 Sep 2019 11:00:07 -0400 (EDT) Date: Wed, 4 Sep 2019 08:00:05 -0700 From: Andres Freund To: Tom Lane Cc: Alvaro Herrera , Bruce Momjian , pgsql-docs@lists.postgresql.org Subject: Re: Release notes on "reserved OIDs" Message-ID: <20190904150005.ncwlp3gxwp7n55ja@alap3.anarazel.de> References: <20190830153424.GA3324@alvherre.pgsql> <29753.1567182909@sss.pgh.pa.us> <20190904094055.og3vq27tj7we7x4n@alap3.anarazel.de> <22548.1567604503@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <22548.1567604503@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi, On 2019-09-04 09:41:43 -0400, Tom Lane wrote: > Andres Freund writes: > > On 2019-08-30 12:35:09 -0400, Tom Lane wrote: > >> I think it's the sort of thing that we sometimes cover in the > >> "source code" changes of the release notes. But yeah, 09568ec3d's > >> idea was pretty much fully superseded by a6417078c, so if we're > >> going to document anything it should be the latter not the former. > > > Hm - not sure I see how a6417078c supersedes 09568ec3d, on the rationale > > that we'd discussed in the thread, which the commit message sums up as: > > Add a note suggesting that oids in forks should be assigned in the > > 9000-9999 range. > > As forks != extensions, the release note entry seems misleading, and > > a6417078c doesn't seem relevant? > > If we were trying to honor that rule, we'd be asking patches to use > temporary OIDs that don't fall into the 9K range. Otherwise, a fork > that thinks it has private OIDs up there is going to have intermittent > trouble tracking HEAD. Given the timeline 09568ec3d really couldn't forsee a6417078c... > As things stand after a6417078c, the safest place for a fork to put > private OIDs is actually from 7999 down; patches shouldn't touch that > range, and it'll be a long time till we hit it working up. Should we just update the comment to reference that then? Greetings, Andres Freund