Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sOJTE-00DbyO-3j for pgsql-pkg-debian@arkaria.postgresql.org; Mon, 01 Jul 2024 16:01:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sOJTC-0033wm-Hk for pgsql-pkg-debian@arkaria.postgresql.org; Mon, 01 Jul 2024 16:01:34 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sOJTC-0033wd-Ac for pgsql-pkg-debian@lists.postgresql.org; Mon, 01 Jul 2024 16:01:34 +0000 Received: from mail-lf1-x131.google.com ([2a00:1450:4864:20::131]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sOJTA-004VpO-8q for pgsql-pkg-debian@postgresql.org; Mon, 01 Jul 2024 16:01:33 +0000 Received: by mail-lf1-x131.google.com with SMTP id 2adb3069b0e04-52ce17f6835so372515e87.1 for ; Mon, 01 Jul 2024 09:01:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=crunchydata.com; s=google; t=1719849690; x=1720454490; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=f4o2z3bMJiqIEFeCFlc+q8ydMKQiajnxrVBRn/d+xfE=; b=p8nz84uc0rnTf6DdaOO+gn5maLbNcSfGsA7i4mmkyWtthsTKRqmVXP07IlkvGeLTtB AiKQiaGwy4nnRSL8RH7LflLkOEXlIZBPXJOqgF1egiw9SFjN8N62HWeTyTiOBWY0mqAg I+XW2DFsm+ER15WEgNNcexIDVhMSxvTl87CEmcqzlePQQ6UlCwLmzIhzU9hh3vUNWIpb RADeku10R2MFs+YwMAcnzQGkOfltlCv3eU00U7JTCNw8P50GtYoxvi+7LYLqFOhQ3pvz DvjJsqTFgJEcFcwUXace1p58woB/Rrc8FAUiE1lWSe+uPMUVn1j1U9Sg14JQeA8w/o9k njSA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719849690; x=1720454490; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=f4o2z3bMJiqIEFeCFlc+q8ydMKQiajnxrVBRn/d+xfE=; b=kzWENKvqJ4ia/+6oUBnyqLPsWcQ2Mhmufb+5mdm75v0nVOmR0zlkq8F31aoM3A80Bj fq2EJ4xDeeCu4ZaF6vSQ+PLvl/hgI9RUbWmGk2/vFb19rDP7vcEPY049GApk4hPY15KK osuBIR+LHozYAJbFsX8nlTmVjMe6DDe2R0VBf5EX2OOpKoSFjrEyUA2Aeg+/ZH/pKTj9 Cmsh/+WmYhwV6lmkQJR0mU3J7HaabCEHyqM3XrlUsX2Wbmv0GX9C9BWCmYy5xTDOWd8v rte9IX2arXp0ALI1z6B2TBl6DwNlJVbTI04R+77hwe0eIDyjSHIg2QuDOtuPiAhGkqUo W1vw== X-Gm-Message-State: AOJu0YzV69l69Py9ZZ9y+tUxOW32aDbnJR3rADx1J8J0op5UjZgvmEZt Ae+XJYWu84D6VX9oMeLP1s+p0dPLbuwLfPexe1KBPkvXeqZZDOR+6eQpydGTflwEwTF1h4RGHqW SW2YCphaJSizEv3BZpzG1S8FhfuxuLFX6/WyKVvVy4iYEDefeA08= X-Google-Smtp-Source: AGHT+IG/Ac0PCBYMTg+k7FCh0DxtkQKadZZkkrZnTCtXNiCqUVQMCJQ5bAh+sHVs6vBWn715TRf5+iyAocvLWZaviO8= X-Received: by 2002:a05:6512:4021:b0:52c:a88c:1db8 with SMTP id 2adb3069b0e04-52e826607f1mr3642119e87.2.1719849690056; Mon, 01 Jul 2024 09:01:30 -0700 (PDT) MIME-Version: 1.0 From: Greg Smith Date: Mon, 1 Jul 2024 12:01:19 -0400 Message-ID: Subject: PostGIS files for PG17-b2 To: pgsql-pkg-debian@postgresql.org Content-Type: multipart/alternative; boundary="000000000000d7e76e061c31b5f2" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000d7e76e061c31b5f2 Content-Type: text/plain; charset="UTF-8" I'm trying to run performance tests for the PG17-b2 release, but like b1 I don't find the PostGIS files there to complete my test suite, Normally I'd use: sudo apt install postgresql-17-postgis-3 postgresql-17-postgis-3-scripts But I don't see any of that available yet for 24.04 Noble Numbat. Is that normal? Should I get those from somewhere else? I know this package repo normally supplies them for the final release. P.S.: there is a cat bump for 17b2 and you give out pg_upgrade instructions that correctly move the cluster to the new version. Works great. However, the final cleanup step recommended doesn't work: postgres@rising:~/pgbench-tools$ rm -rf /var/tmp/postgresql-17-202405161 rm: cannot remove '/var/tmp/postgresql-17-202405161/bin/pg_resetwal': Permission denied rm: cannot remove '/var/tmp/postgresql-17-202405161/bin/pg_walsummary': Permission denied ... rm: cannot remove '/var/tmp/postgresql-17-202405161/lib/plpgsql.so': Permission denied I needed an account with sudo to wipe that directory out: sudo rm -rf /var/tmp/postgresql-17-202405161 Not sure how you want to deal with this, seems like a rough edge that should be polished before release. -- Greg Smith greg.smith@crunchydata.com Director of Open Source Strategy --000000000000d7e76e061c31b5f2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I'm trying to run performance tests for the PG17-= b2 release, but like b1 I don't find the PostGIS files there to complet= e my test suite, =C2=A0Normally I'd use:

sudo apt install postgr= esql-17-postgis-3 postgresql-17-postgis-3-scripts

But I don't se= e any of that available yet for 24.04 Noble Numbat.=C2=A0 Is that normal?= =C2=A0 Should I get those from somewhere else?=C2=A0 I know this package re= po normally supplies them for the final release.

P.S.: =C2=A0there i= s a cat bump for 17b2 and you give out pg_upgrade instructions that correct= ly move the cluster to the new version.=C2=A0 Works great.=C2=A0 However, t= he final cleanup step recommended doesn't work:

postgres@rising:= ~/pgbench-tools$ rm -rf /var/tmp/postgresql-17-202405161
rm: cannot remo= ve '/var/tmp/postgresql-17-202405161/bin/pg_resetwal': Permission d= enied
rm: cannot remove '/var/tmp/postgresql-17-202405161/bin/pg_wal= summary': Permission denied
...
rm: cannot remove '/var/tmp/p= ostgresql-17-202405161/lib/plpgsql.so': Permission denied

I need= ed an account with sudo to wipe that directory out:
sudo rm -rf /var/tmp= /postgresql-17-202405161

Not sure how you want to deal with this, se= ems like a rough edge that should be polished before release.

=
--
Greg Smith=C2=A0 greg.smith@crunchydata.com<= br>Director of Open Source Strategy
--000000000000d7e76e061c31b5f2--