Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1flD1X-00088a-K9 for pgsql-general@arkaria.postgresql.org; Thu, 02 Aug 2018 12:48:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1flD1V-0006Br-Ib for pgsql-general@arkaria.postgresql.org; Thu, 02 Aug 2018 12:48:09 +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.89) (envelope-from ) id 1flD1S-0005v7-7i for pgsql-general@lists.postgresql.org; Thu, 02 Aug 2018 12:48:07 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1flD1O-0008TY-Sz for pgsql-general@postgresql.org; Thu, 02 Aug 2018 12:48:05 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id B3FFD21ADF; Thu, 2 Aug 2018 08:48:01 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Thu, 02 Aug 2018 08:48:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=cI0NIA1zeUTvuWFkOviQ/pkYTbzkf N/PqTMHAUCIpqU=; b=P/Q+CR7fxPPiu6p0RN9ajNvfRh6FAtexKQbIKt5J9BsnE EqXc8WM47thyYeSO0XDt7lA+K4Ppvu4ktYgmzMP48p994FIqGSTTRdIgmjrop9YU e7ZmzRUI5J7bhALu34wvprJmF76Krc4BnODY4GAlp2p+G5aSbqgQdE60qRPs2XZQ uCQWJHcFsyH7I4WtlxbhMYf9AnUkcugJP0OEY0CUSx1mPnnD0MmHUgFpEknGh3k1 VJKUpYtZ4+MJD0hCw8AjVq2DCODOsmuHL3tsA9yKZ6vpy0i6yl+8vtiTT5gg6nus lFFJ/3HP/rfFifqV6DhV7mEFeQnST0NzzHbEpdoDg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=cI0NIA 1zeUTvuWFkOviQ/pkYTbzkfN/PqTMHAUCIpqU=; b=gBSdWukFZF3z4lG2W4QvTi 81CUPoYrtMZ+DaW0uovQs4zics0KTUS1zIFH8D29LIBfBBpVrpWF6K3vlOu7bcbG TfJ0k0pLJepH0ntN7DpqLt/mAV1Wy5XAV7dgKRQmA8HSV8JmtwqDgwLG/MZ+jANB 3Am43HBHLkiBtF6rdTt/2bCXrWKlI2V0FVDr+DlKonRBvOl0C59QYWVy30Asr1Fo lPK8vQPakajbbyNv1tLYa/nReIGI/Cu1bNiHUtqNcDN76yZScBaerX2OMYlc9eZF k3MkRgZkqB0TbDrAc9aGh5tXjUAcIuU0sziDRYtuwiwlZzoCUW2VH0N4rKXSdbTA == X-ME-Proxy: X-ME-Sender: Received: from [192.168.1.3] (unknown [71.212.134.181]) by mail.messagingengine.com (Postfix) with ESMTPA id 0B89BE48A7; Thu, 2 Aug 2018 08:48:00 -0400 (EDT) Subject: Re: Who and How is responsible for released installations packages and 3rd party packs? (e.g. on https://yum.postgresql.org/9.6/redhat/rhel-7.3-x86_64/) To: Alexandru Lazarev , pgsql-general@postgresql.org References: From: Adrian Klaver Message-ID: <6c09d174-7f63-5e84-fedb-31ddbb74a3c6@aklaver.com> Date: Thu, 2 Aug 2018 05:47:59 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 08/01/2018 10:53 PM, Alexandru Lazarev wrote: > Hi PG Community, > > In my company I found that PG Installation on deployed OS Images are > takne from here: https://yum.postgresql.org/9.6/redhat/rhel-7.3-x86_64/ > > We are using PG 9.6.5 or 9.6.7 + pgpool + plv8 + others > > Some or RPMs for CentOS are taken from that URL (PG Installation, plv8). > > My question is: > Who is building RPMs and uploading to that URL? What are the criteria to > build one RPM or other and their versions? https://www.postgresql.org/download/linux/redhat/ https://yum.postgresql.org/ > Why I am asking: > I saw on URL there are PG 9.6.8 and 9.6.9 - Are there maintained only > latest 2 build releases? > > plv8 - there are versions 2.0.0-1 and 2.1.0, since latest plv8 are > already 2.3.7 and latest for 2.1.X is 2.1.3 contating major fixes > > > Thanks, > AlexL -- Adrian Klaver adrian.klaver@aklaver.com