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 1gaNOK-0007FE-Fb for pgsql-pkg-yum@arkaria.postgresql.org; Fri, 21 Dec 2018 16:11: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 1gaNOJ-0005FP-3X for pgsql-pkg-yum@arkaria.postgresql.org; Fri, 21 Dec 2018 16:11:11 +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 1gaNOI-0005FH-SL for pgsql-pkg-yum@lists.postgresql.org; Fri, 21 Dec 2018 16:11:10 +0000 Received: from mail-lf1-x142.google.com ([2a00:1450:4864:20::142]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gaNOG-0003cj-B5 for pgsql-pkg-yum@postgresql.org; Fri, 21 Dec 2018 16:11:10 +0000 Received: by mail-lf1-x142.google.com with SMTP id a16so4284681lfg.3 for ; Fri, 21 Dec 2018 08:11:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hP5GVXgKwF6cugR81vixbB35sxc1WFgCsP83vzoPu2s=; b=hYLr9iFjWUl+6Hmj2Lu/3O3tMxrRfuPQGykNjgsu3PRS+67IcvRkfGN3EjwB5rnOuS HcbkK4bgO97QXLi0tISMsNPq7zH7JqR6/tsjj3SOAEEXN3g74QF9WyakEx/QB6gWTm5Y J6zF4c3iso8PXPKpFp195Klb2sLWSUFBN3n1QedaEib95tLjhUrmo4QDFDWcbM75Vj8d hTxE+6DYFBqzH3lJj5ZxKS304Hj971Z25KKl+WFMM0LDbe0FZaD8IdnvtcwEDab0imb6 3xxO69CCqpgTe8IyH7+tPwLQLymwd6TsKhlYwxMch7QQXK2K3Ikc/t74MD8dGLRtThNN 99aw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hP5GVXgKwF6cugR81vixbB35sxc1WFgCsP83vzoPu2s=; b=cUdFR71T38XiIqjEwvZJpZIzOwkhFfyZ6oEjn9Rd5Lgc8JbbBnaR2PCmajSzQQTFEU vmAMzRXGnMdiVxSLclmI7zx3QfUXJTZoX2RIdZahklKpGtRn+tfJohZlVxMgcSfR/x4j chUGOaZ6LXExHdwBH1FeU5HyHdgZv+6E4pyU5/szpViiHKDCJqGCMf5pivRYV7w6BzZs 1IhWE0TET7SGGbSZqgKqmju/OikYnevi3zgjjYml7hQ8I25JJAK/WAFowMX/2ONTlqd7 wRO8t43wsjrC9tEw/uTgDwVdh+8o+iHHYebrGNuO0Ky9nDAP0Tf/RF6tP5PSu4KwVl4q ODZg== X-Gm-Message-State: AA+aEWZFKIMOsfYQpycfq9Z/IelDoK2ETWf+j0ndRNzBBPh6NPtzgP8e fUNAQwUlifmuFbPL/GCOPmVu6IkF4O5CL/Cs+Vw= X-Google-Smtp-Source: AFSGD/X6GKhrtfeEVrEAJ/9d7fRj7jm73MQaaepmtU+0p24nNc00FEBOf5Ior2H2rLQvNW9Nd5bmrThEQh5ZAemzgWU= X-Received: by 2002:a19:739d:: with SMTP id h29mr1886525lfk.85.1545408667224; Fri, 21 Dec 2018 08:11:07 -0800 (PST) MIME-Version: 1.0 References: <61c1f603a6a2fa7bd38908704ea491e530caafc2.camel@gunduz.org> <20181120115155.5061137f@firost> <20181120122414.73801328@firost> In-Reply-To: From: cwlists Date: Fri, 21 Dec 2018 17:10:54 +0100 Message-ID: Subject: Re: Missing RPM packages at yum.postgresql.org To: =?UTF-8?B?RGV2cmltIEfDvG5kw7x6?= Cc: Jehan-Guillaume de Rorthais , pgsql-pkg-yum@postgresql.org Content-Type: multipart/alternative; boundary="000000000000a48da9057d8a7e7b" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000a48da9057d8a7e7b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Devrim, Only remove if you are absolutely sure it won't break anything. For now I just comment out this part after PG upgrades, which I can live with. BR, Christian On Fri, Dec 21, 2018 at 12:46 PM Devrim G=C3=BCnd=C3=BCz wrote: > > Hi, > > On Sun, 2018-12-02 at 09:38 +0100, cwlists wrote: > > Hi and thank you all! Looks good now :-) > > yw! > > > Devrim, you might not remember me, but I met you at Nasdaq, Stockholm, = a > > couple of years ago when you held a course. I asked you specifically wh= at > > PG HA solution to chose. > > I definitely remember :) > > > I like your packaging work! Btw, I wonder why you include /etc/profile = in > > the .bash_profile explicitly, because at least in my RHEL and CentOS > > installations I notice it is run twice when you login as postgres. Is > there > > a situation when it is not called? Probably in most situations this is > not > > an issue since for example scripts in /etc/profile.d/ should handle > > multiple calls, but I have a script there which can't know if it has be= en > > called before for this login session. > > I think there are/were some historical reasons for that. I can remove tha= t, > unless anyone objects. > > Regards, > > -- > Devrim G=C3=BCnd=C3=BCz > EnterpriseDB: https://www.enterprisedb.com > PostgreSQL Consultant, Red Hat Certified Engineer > Twitter: @DevrimGunduz , @DevrimGunduzTR > --000000000000a48da9057d8a7e7b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Devrim,

Only remove if you are absol= utely sure it won't break anything. For now I just comment out this par= t after PG upgrades, which I can live with.


BR,
Christian

=
On Fri, Dec 21, 2018 at 12:46 PM Devrim G=C3=BCnd=C3=BCz &= lt;devrim@gunduz.org> wrote:

Hi,

On Sun, 2018-12-02 at 09:38 +0100, cwlists wrote:
> Hi and thank you all!=C2=A0 Looks good now :-)

yw!

> Devrim, you might not remember me, but I met you at Nasdaq, Stockholm,= a
> couple of years ago when you held a course. I asked you specifically w= hat
> PG HA solution to chose.

I definitely remember :)

> I like your packaging work! Btw, I wonder why you include /etc/profile= in
> the .bash_profile explicitly, because at least in my RHEL and CentOS > installations I notice it is run twice when you login as postgres. Is = there
> a situation when it is not called? Probably in most situations this is= not
> an issue since for example scripts in /etc/profile.d/ should handle > multiple calls, but I have a script there which can't know if it h= as been
> called before for this login session.

I think there are/were some historical reasons for that. I can remove that,=
unless anyone objects.

Regards,

--
Devrim G=C3=BCnd=C3=BCz
EnterpriseDB: https://www.enterprisedb.com
PostgreSQL Consultant, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR
--000000000000a48da9057d8a7e7b--