Message-ID: <1475789484.3515.54.camel@gunduz.org>
Subject: Re: PostgreSQL Minor Release Retention Policy
From: Devrim =?ISO-8859-1?Q?G=FCnd=FCz?= <devrim@gunduz.org>
To: Jason Petersen <jason@citusdata.com>, pgsql-pkg-yum@postgresql.org
Date: Fri, 07 Oct 2016 00:31:24 +0300
In-Reply-To: <21BD0B07-8861-4F36-A1E1-9D140089CA43@citusdata.com>
References: <21BD0B07-8861-4F36-A1E1-9D140089CA43@citusdata.com>
Content-Type: multipart/signed; micalg="pgp-sha256";
	protocol="application/pgp-signature"; boundary="=-WdrABgn8ASrQPh/iHfZp"
Mime-Version: 1.0
Precedence: bulk
Sender: pgsql-pkg-yum-owner@postgresql.org


--=-WdrABgn8ASrQPh/iHfZp
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


Hi Jason,

On Thu, 2016-10-06 at 14:04 -0600, Jason Petersen wrote:
> In a blog post, Devrim wrote: "This means, when there is new release
> available, we will delete n-3th one. This is a policy to keep the repo cl=
ean.
> This does not apply for PostgreSQL major releases=E2=80=9D
>=20
> I take it this actually means release and not version, right? For instanc=
e,
> last I checked we had 9.5.3-2, 9.5.4-1, and 9.5.4-2 in there. So if I kno=
w
> I=E2=80=99m on 9.5.4, I=E2=80=99m not automatically safe until 9.5.7=E2=
=80=A6 my package may
> disappear as soon as 9.5.5 if there is enough RPM release churn?

repomanage script, ( part of yum-utils and dnf) that we use for cleaning up=
 old
packages, has this option:

=C2=A0 -k KEEP, --keep=3DKEEP=C2=A0=C2=A0newest N packages to keep - defaul=
ts to 1

So, I set -k 3 in our sync scripts.

What does it mean? Under normal circumstances, if we don't make any packagi=
ng
mistakes, when we release 9.5.5, then 9.5.2 will be removed, so we'll keep =
the
latest 3 versions.

However, there is a minor potential problem in here: If we release 9.5.5-2,
then 9.5.3 will be removed, so practically we'll have only 2 versions (?).

> This makes it pretty unsafe to hardcode a full version specifier in e.g. =
a
> Dockerfile or other system meant to produce repeatable results, but I sup=
pose
> people can just run their own package mirrors if they desire a different
> retention policy.

Right.=C2=A0

Why do you hardcode postgresql RPMs in Dockerfile, btw?=C2=A0

Regards,
--=20
Devrim G=C3=9CND=C3=9CZ
EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Dan=C4=B1=C5=9Fman=C4=B1/Consultant, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR

--=-WdrABgn8ASrQPh/iHfZp
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAABCAAGBQJX9sKsAAoJENjDPf6Sz261Dr8P/19ZBcDwXIATCvZAok9C4lSM
3vMnoCytQzLm/nPiQlhFu+mscX/KDuqNIAtgny/+ZjAFHvnUGI2KvDZPVHWmKzgB
P7iI7eIdoryGeXxer++M6v8lwL4oFkmpwc+eEb/hOyMMgNBKjleYJ9Og8EhOOqnS
DFw6xsS2jkUKBaS+NeB1BzyE4dX2yLaCD2tcFpb1vEZlMEEqyrLw/AJ56uFGzJMt
nXqjliAKjvr2IcmX96Dtv04x3hBeuAUMmxNQTiMIS4fgnI5/+U2B1i47No7pehWv
7jSE+lYo85zy0ekKk1pfuQHLi7fPFAv8Wk9Da5xbkpyp+03SHHyMq+eQ9rwBfHCI
bRZfQsLVddwIVTI3JTPqoUT9WURFybSKEVA5g+XfMGFkOuczCRCk76xdAEK8nRlH
jumTlOIqof7kO1qcQPS/wYUtXJwGcJIUOiGoOSYfIf5GwLk6dfBJ/wnQX6JZo2ZF
ylixHvG17RmHK3rBZA3LIHwNp7Z4TrAsyD0uJiXkXr6+Vg7LMBzS0nc18PZvVxkA
cwYCHSUlVe5LfLqCrjeCoC88+JKmw2rSKnm/FQK2yzdfGts210wsWKDPghJnu/O4
CsumWNWylf9TCBr7vgbk0c5EscINlNpiBXRikI9xPmG6hjAh/l9P0DPcTFTSRv7G
ZtcLkv9aKKvDuBV+Bs3g
=q/BA
-----END PGP SIGNATURE-----

--=-WdrABgn8ASrQPh/iHfZp--