[Pkg-postgresql-public] Bug#894327: pgpool2 fails its autopkg tests with OpenJDK 9

[Christoph Berg]

Re: Emmanuel Bourg 2018-03-29 <9eccb955-892a-1c50-1c67-22b76d1c2...@apache.org>
> I'd rather keep libpgjava with the Java Team, but the help from the
> PostgreSQL group is definitely welcome. Please join the pkg-java group
> on Alioth and the java-team group on Salsa, I'll grant you access to the
> repository (we haven't migrated to Salsa yet but we'll do a mass
> transition in the near future).

Hi Emmanuel,

I just requested access. Thanks!

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#894327: pgpool2 fails its autopkg tests with OpenJDK 9

[Christoph Berg]

Re: Matthias Klose 2018-03-29 
> WARNING: Illegal reflective access by org.postgresql.jdbc.TimestampUtils
> (file:/usr/share/java/postgresql.jar) to field 
> java.util.TimeZone.defaultTimeZone
> WARNING: Please consider reporting this to the maintainers of
> org.postgresql.jdbc.TimestampUtils

Hi Matthias,

thanks for the report. As the problem rather seems to be in libpgjava,
and I've been meaning to ask this for quite some time, but always
deferred it:

I'd like to update the PostgreSQL JDBC driver to the current version,
either by doing that within the Java group, or by moving libpgjava to
the PostgreSQL group (and taking care of future updates as well).

Would that be ok? (I don't think I have java commit access on
alioth/salsa yet.)

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Accepted pg-similarity 1.0-1 (source) into unstable

[Christoph Berg]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 27 Mar 2018 10:48:59 +0200
Source: pg-similarity
Binary: postgresql-10-similarity
Architecture: source
Version: 1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 
<pkg-postgresql-public@lists.alioth.debian.org>
Changed-By: Christoph Berg <christoph.b...@credativ.de>
Description:
 postgresql-10-similarity - PostgreSQL similarity functions extension
Changes:
 pg-similarity (1.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * Mark license as BSD rather than MIT, pointed out by Thorsten Alteholz,
 thanks!
   * Move packaging repository to salsa.debian.org
Checksums-Sha1:
 7489becaddca4949e59d60d0b4d3b61349400cb3 2086 pg-similarity_1.0-1.dsc
 aca9e8f5b8c0b64310785f46c7732f63ae736ec6 57558 pg-similarity_1.0.orig.tar.gz
 0442665bb8cd66876e81ba3ea83c9ff8443da375 3368 pg-similarity_1.0-1.debian.tar.xz
 ac27001f92e3179f23035850b395290d68a31750 6914 
pg-similarity_1.0-1_source.buildinfo
Checksums-Sha256:
 af9987fe4253c2151ba9151eea6258d6fe83a1c40eebedb26734af28a52218b8 2086 
pg-similarity_1.0-1.dsc
 0d74e5c6ba3dd753da8bb55293ebb0f05484eab342af5c2ee1fd03a1cd876276 57558 
pg-similarity_1.0.orig.tar.gz
 1e665adf800be22d3741df27e9db0af61b209e4e59a1d7b5dc37eadb5a65c583 3368 
pg-similarity_1.0-1.debian.tar.xz
 69db0be2551d46d64bd7d633ac75b9c5bfaa871dff49257e953831c92980b19c 6914 
pg-similarity_1.0-1_source.buildinfo
Files:
 c4f385ba05dd67bbd988fd554b7e8c84 2086 database optional pg-similarity_1.0-1.dsc
 e8b67f4a4092c19ec10c05bf1f1b157b 57558 database optional 
pg-similarity_1.0.orig.tar.gz
 f091a8522092ebabebb87564fc1a8a6e 3368 database optional 
pg-similarity_1.0-1.debian.tar.xz
 8ec6a9e17e9d70752fe70e33a7ed9514 6914 database optional 
pg-similarity_1.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlq6C+gACgkQTFprqxLS
p66Qzw//Qgh77LeYcmIqaPwZACponvsNhAfHMlhBLvGErx2eCLa3pn1DY19JIyHE
2VGI2+2QVmh7mdClYbg3GFGVLqNgHPoTdaT52OVVdRgquuXB81rC+mtbgBoFUZTn
MJBZ/xjEM9+XmiYzAIYHn8OJ0SY63Oz7/Sc17mAm8i5/bTptrwIT+OmLoql+pJLw
+/G9tOclzr66tA8lLWRkyHFE6PTmmueo0cppGUrpBPqvCo7IXmHC8IcGUxElbEns
tdA1+vnDYo1j2KEcLJsIi2IYjDERj/hJVl97eIBfzrZT3qphFAcjzhgGiqk5VhSs
Pb4gS/WEFs+JxSmizUhAifCexMuuKelDtTTI5+0W0wdUzGdHcQLX6s4Pw7wTnbq0
sB1X064qijS9J9quC0x3q4UbHSwA40nusFPqE0Eo8o6WckoRPpGT4wiS66j4e1V6
/0JEDYGZ3rLNnI41unXZ37E9phyK91dGdWyaoClgtkaStKyBHfZJvHdWngSvIpUK
0cMMwAjdTyX8CJozF+PEbSzmErTHywlt60vikrmhuEniMtRoBkg/bwQpxZkYsbgN
ZHgCoMmg/ZBhesYYG4E5Sbr5dT6IpynJDIQzrcV8Uosl1qeNPMzhWnNxuWFy0P4c
sW2KWWYZtCNep31Pr0eqwgmSqJMzssf+Daxzh/aPZnSWFgIJ4G8=
=ab+m
-END PGP SIGNATURE-


___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] PostgreSQL 10.3 and Ubuntu

[Christoph Berg]

Re: Olleg Samoylov 2018-03-27 <2820501522156...@web55g.yandex.ru>
> Well, I can wait 1 month more. But this is not good for your reputation. I 
> think if just take package scripts from 10+189.pgdg17.04+1
> and rebuild package with modern postgresql 10.3 source it will work.

"Just" is not just that, but setting up the repository, bootstrapping
the PG packages, and then rebuilding all other package on top of that.
The whole process takes several days. Including QA, we would barely
finish before 18.04 gets released.

Sorry. We'll do better next time.

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Accepted postgresql-10 10.3-2 (source) into unstable

[Christoph Berg]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 21 Mar 2018 13:56:34 +0100
Source: postgresql-10
Binary: libpq-dev libpq5 libecpg6 libecpg-dev libecpg-compat3 libpgtypes3 
postgresql-10 postgresql-client-10 postgresql-server-dev-10 postgresql-doc-10 
postgresql-plperl-10 postgresql-plpython-10 postgresql-plpython3-10 
postgresql-pltcl-10
Architecture: source
Version: 10.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 
<pkg-postgresql-public@lists.alioth.debian.org>
Changed-By: Christoph Berg <christoph.b...@credativ.de>
Description:
 libecpg-compat3 - older version of run-time library for ECPG programs
 libecpg-dev - development files for ECPG (Embedded PostgreSQL for C)
 libecpg6   - run-time library for ECPG programs
 libpgtypes3 - shared library libpgtypes for PostgreSQL 10
 libpq-dev  - header files for libpq5 (PostgreSQL library)
 libpq5 - PostgreSQL C client library
 postgresql-10 - object-relational SQL database, version 10 server
 postgresql-client-10 - front-end programs for PostgreSQL 10
 postgresql-doc-10 - documentation for the PostgreSQL database management system
 postgresql-plperl-10 - PL/Perl procedural language for PostgreSQL 10
 postgresql-plpython-10 - PL/Python procedural language for PostgreSQL 10
 postgresql-plpython3-10 - PL/Python 3 procedural language for PostgreSQL 10
 postgresql-pltcl-10 - PL/Tcl procedural language for PostgreSQL 10
 postgresql-server-dev-10 - development files for PostgreSQL 10 server-side 
programming
Closes: 891898 892807
Changes:
 postgresql-10 (10.3-2) unstable; urgency=medium
 .
   * Improve wording of NEWS entry on search_path changes. Thanks Chris Lamb!
 (Closes: #891898)
   * Disable spinlocks on riscv64, thanks Aurelien Jarno! (Closes: #892807)
   * B-D on python3-distutils | python3-dev (<< 3.6.4~rc1-2).
Checksums-Sha1:
 705d70eee482655783a6c672895b87622969c5db 3524 postgresql-10_10.3-2.dsc
 02fa752b1b72bc81d488080d2971f634a88dc180 23032 
postgresql-10_10.3-2.debian.tar.xz
 ba3cdf8aa980b6eb16b4e774d23a8dc942084563 8184 
postgresql-10_10.3-2_source.buildinfo
Checksums-Sha256:
 1f3d0d9204d40631a5e6b775a285868cdccd4fe69deba8b8967cad7eb219ae33 3524 
postgresql-10_10.3-2.dsc
 e06aa0fc38f0900dff89c4a1e2a3229fa3e3df70d533e68fd02e1ff726ace9ac 23032 
postgresql-10_10.3-2.debian.tar.xz
 d483020a74c1ea8eee2f05593240d4fd26cfadfee8f3acda9c603283c9d927fe 8184 
postgresql-10_10.3-2_source.buildinfo
Files:
 378fe68e7e54b7df4d3d974da8c40364 3524 database optional 
postgresql-10_10.3-2.dsc
 0c8b72df0d971b0ec11c6a5110876662 23032 database optional 
postgresql-10_10.3-2.debian.tar.xz
 72be9a2fa660db03a7ecb38c3e5f7ff9 8184 database optional 
postgresql-10_10.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlqyVtIACgkQTFprqxLS
p67rUBAApgefMTlL3hQJtZCF+lOLKu1DQefZxCZjMI7QbMn3CJsXyNXTKwSUF/Cn
Sz2UfI8pJerPMxVyy0vPcP3qfz8SWQGJNo+oSJRtu7cKJfbnMU2wTjAZ66aqJU1u
kHUN7e4UHgwCZQg3MTzpum9RWpWDB6XfFsK38XUVtLpQih/Zyo3XT2reLuQcj9/q
TLtlA9y3ct57kl3jOlwldUjmlSnrSU5JyEMiaKbmEu6pUX5WV63ejEmQ0LXRYgbj
Ha4qjihrjX/3m2PWWzovTHyk89ZcMKf3A0GSb6i2V8nWcjobsfT77QQnVIdsJm/w
m8vFiEFPgy63nmRm3BAPD1wm5IYBf/tnZCOoqr60gsuK+CvODSJAJtZSJrKaG/Na
eHrTgGfTHaMLyC2L5Zgsko/p0CLCcwW9Dbn6eDNyfxPlL4sMuPMsahtRd9vu0irt
jIRLT1TwVZsqHxsiSkhVc4ERd0FH0QoIiTjIQhKKnksm557UL+tim5b0cbjU/KP3
2c6ABiU8F7larT0SUPtDlYqCPJ/fEAEtogqMSRUUjUeiSwKuCRNkZl3blp4cQbtw
Sjyj6eAyHqaU5UbUIndu+NSJaOEW6UodpRiCkJxLGjttGgraM+MkiWkxj+crfToa
+dBY/UtWNpYVmL8/423jFblx33LZBeK4iRO3rOc1ugtMbL8eXYI=
=au/s
-END PGP SIGNATURE-


___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Accepted pspg 1.0.0-1 (source) into unstable

[Christoph Berg]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 19 Mar 2018 09:13:21 +0100
Source: pspg
Binary: pspg
Architecture: source
Version: 1.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 
<pkg-postgresql-public@lists.alioth.debian.org>
Changed-By: Christoph Berg <christoph.b...@credativ.de>
Description:
 pspg   - PostgreSQL pager
Changes:
 pspg (1.0.0-1) unstable; urgency=medium
 .
   * New upstream version.
Checksums-Sha1:
 bb4b3bb18a6a47518cb323b4f83be9dc0afbc5cc 1983 pspg_1.0.0-1.dsc
 5b4876cfc78b04b38ea0cde01bf70a9278690dbe 858176 pspg_1.0.0.orig.tar.gz
 d0810d6fee983745ed81a237f8d87abc84dc0d74 2500 pspg_1.0.0-1.debian.tar.xz
 1976afd5ef5779390dc971bc72408d304ca8be3b 5276 pspg_1.0.0-1_source.buildinfo
Checksums-Sha256:
 93bdc1bb0898383087851f8755868b70f60542f642a27ac1ba988260bb11d0e9 1983 
pspg_1.0.0-1.dsc
 1035015f8fb29c749d5c1d023db0c391c79c2fa7180cfecdf788dd7e9c9a0fbc 858176 
pspg_1.0.0.orig.tar.gz
 b943a186d055b84b12bd0e5596a1a23a596c22711f59438f1d3c627ead8685ef 2500 
pspg_1.0.0-1.debian.tar.xz
 fead6ccd913f5ec5566b604c2188575293044690602014523e5162ac633a8573 5276 
pspg_1.0.0-1_source.buildinfo
Files:
 648f34ea883903fee8ef70c8327bfafe 1983 database optional pspg_1.0.0-1.dsc
 68ce973825d73f562544665d753b4a08 858176 database optional 
pspg_1.0.0.orig.tar.gz
 63108807d2dbc1ab4f2ab65d60e1c1f8 2500 database optional 
pspg_1.0.0-1.debian.tar.xz
 4c524e2e1e2feddfeedc0bc0e8970725 5276 database optional 
pspg_1.0.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlqveuYACgkQTFprqxLS
p66Idw/7BuiwvDVJL651zqJcrkw7CTT/WE99BVjSd4ld1Vh0+p7T7+AJs7XdzjJW
KfxMLdjJ+m/jTB1mJzWMr5Eeh8ea8yUtO4H8alIWZ1zdlRVbt6a5v/Kc+i58dWLp
BNdUE8oWhwgriMsdiawpSIZzxRrpiz2AiS8IKH2F1hEpf9VofjNnfmPngRcH1eqm
+03+0a4cgcCamMz3ygEPUteimbRvj/MdKF0zBJyJGjDyxXG0NFBrUxYzMR5V1kxg
tciiaoC49V6W5yI8KKN2TuLbSK4twuX4V8dl0q8azEa3z+gdD2rbQg5ypmvMehB4
sPMkrzK7PDA5t+AzzGXIskPBKlCrTyiKqVuZgB4Hj5KMS/tQ08AoUDAdRpGnmrgz
x36sQDAPz3vP7g+erEq3vNhzOydK03o3437FwCYd9cS2IRvAPgmB/Z2fm6ayfQoq
F/rDx6lRxbVkTEBNVoGPqomGr9BsILpSjRvqE0gZycPQ3pII2kTHSAlEt4m8SlZr
qBEKL+38oesuGcrhNjXauvOx0W7q8SRAe5NNiS3MY4AavgUodGG0aczHgW8lA548
GJDv+vfJ+DWqZAP10t2KP+V5LdPM7dr+Y7cYe9m9juflEkrn3/0w9UADOLcmIWGv
O1I/V1eIb2CCZic15N0sJSRwgbGs5WkophOhlZlkCTbAV5cn3HQ=
=Ha12
-END PGP SIGNATURE-


___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#795729: Bug#795729: closed by Christoph Berg <m...@debian.org> (Bug#795729: fixed in libpqtypes 1.5.1-3)

[Christoph Berg]

Re: Chris Lamb 2018-03-17 
<1521313480.1891152.1306660656.6a987...@webmail.messagingengine.com>
> Hi Christoph:
> 
> > (I'd rather not put a workaround like TZ=UTC
> > into debian/rules as it would just paper over the issue
> 
> Nod…
> 
> >   * Set TZ=UTC to avoid build failure with TZ=Etc/GMT+12.
> 
> … hang on! Can you clarify? :-)

libpqtypes is pretty much dead upstream. I'd rather have it build
{sanely|reproducibly} using a hack, than not at all.

If I recall the issue correctly, the problem is only visible when
using an artificial timezone like GMT+N, but not when using the
standard ones (Europe/Berlin). So it's not even a real problem in
practise. (What I wrote in the bug about it being a PostgreSQL bug was
a red herring.)

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Accepted libpqtypes 1.5.1-3 (source) into unstable

[Christoph Berg]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 17 Mar 2018 17:08:43 +0100
Source: libpqtypes
Binary: libpqtypes-dev libpqtypes0
Architecture: source
Version: 1.5.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 
<pkg-postgresql-public@lists.alioth.debian.org>
Changed-By: Christoph Berg <m...@debian.org>
Description:
 libpqtypes-dev - parameterized queries libpq extension - development
 libpqtypes0 - parameterized queries libpq extension - shared library
Closes: 795729
Changes:
 libpqtypes (1.5.1-3) unstable; urgency=medium
 .
   * Set TZ=UTC to avoid build failure with TZ=Etc/GMT+12.
 (Closes: #795729)
   * Remove explicit libpqtypes0-dbg package.
   * Move packaging repository to salsa.debian.org
Checksums-Sha1:
 41449ab84dd308bf4b482b89b0f1d628babca5d9 2061 libpqtypes_1.5.1-3.dsc
 8cda08c242d3ab3e9d159a36ec374bd319adf172 3544 libpqtypes_1.5.1-3.debian.tar.xz
 56c78d31a6ae4f3b180f4c48102e65214cb31a30 6417 
libpqtypes_1.5.1-3_source.buildinfo
Checksums-Sha256:
 652fe63899c399970d4f31b4e2e5aa4d013a03c5d1e26b5ee6753c9e2a02d965 2061 
libpqtypes_1.5.1-3.dsc
 fe507884a02b8445f22aad0cc093431e4d831a73d13b60d71dc245c7e6dc9421 3544 
libpqtypes_1.5.1-3.debian.tar.xz
 0bdbb8a57c6a710947749e98e505d1bebf784b8dd5b8e8cb08f9767cdc35b008 6417 
libpqtypes_1.5.1-3_source.buildinfo
Files:
 e6c95c165da705f6b459a3930b79dbfe 2061 database optional libpqtypes_1.5.1-3.dsc
 12c36faadb84233d7c9f06253ae9cabb 3544 database optional 
libpqtypes_1.5.1-3.debian.tar.xz
 14380089cae4a10a85bb4cd9aa0aa40c 6417 database optional 
libpqtypes_1.5.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlqtSM4ACgkQTFprqxLS
p67FPw/+KVwwr/prshXRjrNWkv6ErpkjaxkgFp13fStnrJNtpWDoY/OuqafizbKa
gcoz0ZFokpwnryMZHqA3pT8ujP3cv/C3Y89tUCWap3cQgTpRAMDprwRL4qPR0zqP
ACJM9+rLAwvWQ8BcboX/SU6/QylEI1NyPPAnyRtveibVLoLL72k5DB5gKa8ubeQg
QvColT3Z7y1OLZ3nqo5lsPNeebyihdDut2Itk4QSlhq8w6hC7uiivEUAb+Q4N+TI
yYMpYRky79CAO4KNGXAKsGzow7kY8CZXg0sX4fDGrA5XyWNkBTj4iyv6qkGblrJW
ktf/dkjwf3tPZ9kTA3MZJvKFH3RLLktsaPG8yjVTT76w9chM4WJS8tslyetYRwKv
nhVCqmqdlC/QVGLAJ+9rFEBBYg/37GW4R5lS5MfpTQJ5ZQlzdjhxg6b+LWMdxL0I
+3R3tNWFrHn4Q12NyXXDQBpLN9Sjuy/JLzJMqohpIRg8MqWy2uv427l5URXGT5vQ
Hv1zf5DKpRDcx/j7lFzdYJv+1FwKj5ROogNyr58RBlz1S25XF+b4or8bISmuU6BN
hr/mf8vwhvMc1vU15Z5uHYGiUYnAoe/qyxXXnTtnkBThPseHtdK6q/jetq0Ecczq
aCDWB9BwSdMc43bh8PboYKtXruq7NSVwiNAC68wk6jMGxpyUqbY=
=AjuH
-END PGP SIGNATURE-


___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Accepted postgresql-mysql-fdw 2.4.0-1 (source) into unstable

[Christoph Berg]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 17 Mar 2018 16:46:53 +0100
Source: postgresql-mysql-fdw
Binary: postgresql-10-mysql-fdw
Architecture: source
Version: 2.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 
<pkg-postgresql-public@lists.alioth.debian.org>
Changed-By: Christoph Berg <m...@debian.org>
Description:
 postgresql-10-mysql-fdw - Postgres 10 Foreign Data Wrapper for MySQL
Changes:
 postgresql-mysql-fdw (2.4.0-1) unstable; urgency=medium
 .
   * New upstream version.
   * Move packaging repository to salsa.debian.org
Checksums-Sha1:
 74a6d4085830f558ae7fcf9a1bd08a4d018c3150 2293 postgresql-mysql-fdw_2.4.0-1.dsc
 670adca9b50e8550558827811d28f72833407189 42257 
postgresql-mysql-fdw_2.4.0.orig.tar.gz
 3dcd69cffaa1807387a8751fc8e5e6152da9dec1 5504 
postgresql-mysql-fdw_2.4.0-1.debian.tar.xz
 5315a5f10be685fafd3543ad3fb415916f1b0c12 7401 
postgresql-mysql-fdw_2.4.0-1_source.buildinfo
Checksums-Sha256:
 607a23ea09c6c3693b0e225441f78751ab1e86fd3eb6ead7797fa0e76837a1ab 2293 
postgresql-mysql-fdw_2.4.0-1.dsc
 c55af6f1590e3555e6decdb01ba9975c64ddead8422d565ec975bc5a9a393b95 42257 
postgresql-mysql-fdw_2.4.0.orig.tar.gz
 b5e0e34b520dfd3a2f25e6a148814b73a4198cd2bd498bb26ff35c4d5fa2bcef 5504 
postgresql-mysql-fdw_2.4.0-1.debian.tar.xz
 adc6ee7fc905b117f0d8d061b54ec743708f34f6e29d42342b120a7879c7470b 7401 
postgresql-mysql-fdw_2.4.0-1_source.buildinfo
Files:
 c3c5bdbc22be1f48a409187ba0dde43e 2293 database optional 
postgresql-mysql-fdw_2.4.0-1.dsc
 1ac35be0c7f816e0bb9ec13ec2ff5859 42257 database optional 
postgresql-mysql-fdw_2.4.0.orig.tar.gz
 d88706a444c806958a00d24466658562 5504 database optional 
postgresql-mysql-fdw_2.4.0-1.debian.tar.xz
 df53e4bfb59577a3622fce1126a1d5f7 7401 database optional 
postgresql-mysql-fdw_2.4.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlqtRf0ACgkQTFprqxLS
p652PhAApNyDyoiu6mZ6HfwyJgKOC17BTy4PRyijR0bF/nnA9NehVoMhN5Ef5MyD
5nbi2JqAxnJnOhaPWSfOvU5s8UG7uxKGsXliebXnkrjFLR2e4HOQdRHNt7Cj8GTm
u8FWmgpmK3S6Dakm7oHNutQ0wbaketd9QcG2ieZEdA52sNemdJ8z73Kyg5miZxqs
KzYEtGJGtTEVm/jZcXTvryA7+Qc0E9RBnQi/HxCp9NFlMG4FR8hiw3ztDzsWZwDU
nGycIoJumlBbSFUIYNETrKQygV3VEJ3GwbDiY0lNjoX0n8C54EuCAG26Cmyq25ac
BdEM25DKkVeSqenCDPGJ6KgIhx/qsp6LfobmUNW/+6elN563gyUpr9YO1v2f9rqm
1wEIc8uFzsgHQur0WCSMFy4pQwErwg2nuUGs/PdWV5HPg/8pAUM70XdWpxi8ny5L
XTxNxsqSY50cUTnW4l9lwffWRiLVPUU+ivTIQAwD43pgsmF7b2a+UkcO123/q+32
q0xVR7MDBJoyDz8ZIbuVUUk3b1DcNFEXdpoYPiectAS1VAu2Q4HT9lEgzIzk4EY0
Laob25xSrnsXhaUfp56d4hCX3EZG54ttpPQZkrVuqNNUVJ/OAXTAx7pBT8uQMggR
53pLvNhkwYCYpdfctWtMr9kaKhuUL15egX1n/FvUf2KORNfjEoY=
=l9QP
-END PGP SIGNATURE-


___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] Bug#892807: postgresl-10: please disable spinlocks on riscv64

[Christoph Berg]

Re: Adrian Bunk 2018-03-13 <20180313125337.GK20833@localhost>
> On Tue, Mar 13, 2018 at 02:37:27PM +0200, Adrian Bunk wrote:
> > reassign src:postgresl-10 10.3-1
> > thanks
> > 
> > There is no postgresl-10 binary package, moving to the source package.
> >...
> 
> There actually is (my blindness), actual problem was a missing "q"
> in postgres*q*l.

It's more of a source package fix anyway. Thanks! :)

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Accepted postgresql-9.6 9.6.8-0+deb9u1 (source) into proposed-updates->stable-new, proposed-updates

[Christoph Berg]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 27 Feb 2018 13:14:39 +0100
Source: postgresql-9.6
Binary: libpq-dev libpq5 libecpg6 libecpg-dev libecpg-compat3 libpgtypes3 
postgresql-9.6 postgresql-9.6-dbg postgresql-client-9.6 
postgresql-server-dev-9.6 postgresql-doc-9.6 postgresql-contrib-9.6 
postgresql-plperl-9.6 postgresql-plpython-9.6 postgresql-plpython3-9.6 
postgresql-pltcl-9.6
Architecture: source
Version: 9.6.8-0+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 
<pkg-postgresql-public@lists.alioth.debian.org>
Changed-By: Christoph Berg <christoph.b...@credativ.de>
Description:
 libecpg-compat3 - older version of run-time library for ECPG programs
 libecpg-dev - development files for ECPG (Embedded PostgreSQL for C)
 libecpg6   - run-time library for ECPG programs
 libpgtypes3 - shared library libpgtypes for PostgreSQL 9.6
 libpq-dev  - header files for libpq5 (PostgreSQL library)
 libpq5 - PostgreSQL C client library
 postgresql-9.6 - object-relational SQL database, version 9.6 server
 postgresql-9.6-dbg - debug symbols for postgresql-9.6
 postgresql-client-9.6 - front-end programs for PostgreSQL 9.6
 postgresql-contrib-9.6 - additional facilities for PostgreSQL
 postgresql-doc-9.6 - documentation for the PostgreSQL database management 
system
 postgresql-plperl-9.6 - PL/Perl procedural language for PostgreSQL 9.6
 postgresql-plpython-9.6 - PL/Python procedural language for PostgreSQL 9.6
 postgresql-plpython3-9.6 - PL/Python 3 procedural language for PostgreSQL 9.6
 postgresql-pltcl-9.6 - PL/Tcl procedural language for PostgreSQL 9.6
 postgresql-server-dev-9.6 - development files for PostgreSQL 9.6 server-side 
programming
Changes:
 postgresql-9.6 (9.6.8-0+deb9u1) stretch; urgency=medium
 .
   * New upstream version.
 .
 If you run an installation in which not all users are mutually
 trusting, or if you maintain an application or extension that is
 intended for use in arbitrary situations, it is strongly recommended
 that you read the documentation changes described in the first changelog
 entry below, and take suitable steps to ensure that your installation or
 code is secure.
 .
 Also, the changes described in the second changelog entry below may
 cause functions used in index expressions or materialized views to fail
 during auto-analyze, or when reloading from a dump.  After upgrading,
 monitor the server logs for such problems, and fix affected functions.
 .
 + Document how to configure installations and applications to guard
   against search-path-dependent trojan-horse attacks from other users
 .
   Using a search_path setting that includes any schemas writable by a
   hostile user enables that user to capture control of queries and then
   run arbitrary SQL code with the permissions of the attacked user.  While
   it is possible to write queries that are proof against such hijacking,
   it is notationally tedious, and it's very easy to overlook holes.
   Therefore, we now recommend configurations in which no untrusted schemas
   appear in one's search path.
   (CVE-2018-1058)
 .
 + Avoid use of insecure search_path settings in pg_dump and other client
   programs
 .
   pg_dump, pg_upgrade, vacuumdb and other PostgreSQL-provided applications
   were themselves vulnerable to the type of hijacking described in the
   previous changelog entry; since these applications are commonly run by
   superusers, they present particularly attractive targets.  To make them
   secure whether or not the installation as a whole has been secured,
   modify them to include only the pg_catalog schema in their search_path
   settings. Autovacuum worker processes now do the same, as well.
 .
   In cases where user-provided functions are indirectly executed by these
   programs -- for example, user-provided functions in index expressions --
   the tighter search_path may result in errors, which will need to be
   corrected by adjusting those user-provided functions to not assume
   anything about what search path they are invoked under.  That has always
   been good practice, but now it will be necessary for correct behavior.
   (CVE-2018-1058)
Checksums-Sha1:
 c7bcea2bc6c27b602027e931d80e7a917b082bc5 3694 postgresql-9.6_9.6.8-0+deb9u1.dsc
 8e610dd8dbaab69982d12324971b0c6b5225142f 19528927 
postgresql-9.6_9.6.8.orig.tar.bz2
 3b8957550448a7337d078eefc9f102f34b5f2c7a 23000 
postgresql-9.6_9.6.8-0+deb9u1.debian.tar.xz
 8a147516e8dc0038a5bb4b06fc3393dfdc8f6839 8653 
postgresql-9.6_9.6.8-0+deb9u1_source.buildinfo
Checksums-Sha256:
 415ef4a3d1cf94881b30b631232a01d57d48ec9ba809d94d18c468024e8c828b 3694 
postgresql-9.6_9.6.8-0+deb9u1.dsc
 eafdb3b912e9ec34bdd28b651d00226a6253ba65036cb9a41cad2d9e82e3eb70 19528927 
postgresql-9.6_9.6.8.orig.tar.bz2
 98b2188e97de64729795c2ec33617f5495af7eb2b64ea83138f7

Re: [Pkg-postgresql-public] PostgreSQL 10.3 and Ubuntu

[Christoph Berg]

Re: Olleg Samoylov 2018-03-07 <4428841520416...@web52j.yandex.ru>
> I sent this email to this address because it mentioned in the package as 
> package maintainer.
> 
> There is PostgreSQL 10.3 already. I have Ubuntu 17.10 (artful) and there 
> is not a pgdg repository for it. There is PostgreSQL 10.3 in 16.04 LTS 
> (xenial) pgdg repository, but such packages can't be installed on 17.10 
> (artful) Ubuntu. And there is zesty-pgdg (for 17.04 Ubuntu), works fine 
> for me (for 17.10 Ubuntu), but there are only old PostgreSQL 
> 10+189.pgdg17.04+1. Can you rebuid packages for the zesty or create for 
> the artful with modern 10.3 PostgreSQL?

Hi Olleg,

we can't build packages for zesty because Ubuntu removed zesty from
their mirrors.

We skipped artful because time was limited and went straight to bionic
(18.04). I haven't tried, but there's a chance these packages work on
artful.

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#891687: postgresql-common: dsfwew

[Christoph Berg]

Re: Daniel Kahn Gillmor 2018-02-28 
<151977883437.31585.3826803256327598913.report...@alice.fifthhorseman.net>
> In particular, a user .service named "exampled" which keeps its
> state in `~/.config/example`.  An `exampled.service` unit might be
> configured with:
> 
> Requires=pgcluster@example.service
> After=pgcluster@example.service
> 
> So that if the user service is ever started, the cluster will be
> created on demand (in `~/.config/example/data`) and the "example"
> database will be ready for use (via unix-domain sockets in
> `$XDG_RUNTIME_DIR/example/`) before the user service is started.

Hi Daniel,

this is very interesting, especially Type=notify. I haven't yet had
time to look closely at the patches - my first question would be if we
could integrate the idea more tightly with the existing postgresql@
services which are already capable of launching clusters for different
users (though currently hardcoded to /etc/postgresql/*). The cluster
machinery itself (pg_ctlcluster and friends) can operate on different
roots if PG_CLUSTER_CONF_ROOT is set. Maybe that can be incorporated
to work better together.

One thing I have been thinking about was to replace pg_ctlcluster with
something more systemd-specific, including Type=notify operation. This
looks about what you have here.

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Accepted postgresql-10 10.3-1 (source) into unstable

[Christoph Berg]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 27 Feb 2018 12:54:34 +0100
Source: postgresql-10
Binary: libpq-dev libpq5 libecpg6 libecpg-dev libecpg-compat3 libpgtypes3 
postgresql-10 postgresql-client-10 postgresql-server-dev-10 postgresql-doc-10 
postgresql-plperl-10 postgresql-plpython-10 postgresql-plpython3-10 
postgresql-pltcl-10
Architecture: source
Version: 10.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 
<pkg-postgresql-public@lists.alioth.debian.org>
Changed-By: Christoph Berg <christoph.b...@credativ.de>
Description:
 libecpg-compat3 - older version of run-time library for ECPG programs
 libecpg-dev - development files for ECPG (Embedded PostgreSQL for C)
 libecpg6   - run-time library for ECPG programs
 libpgtypes3 - shared library libpgtypes for PostgreSQL 10
 libpq-dev  - header files for libpq5 (PostgreSQL library)
 libpq5 - PostgreSQL C client library
 postgresql-10 - object-relational SQL database, version 10 server
 postgresql-client-10 - front-end programs for PostgreSQL 10
 postgresql-doc-10 - documentation for the PostgreSQL database management system
 postgresql-plperl-10 - PL/Perl procedural language for PostgreSQL 10
 postgresql-plpython-10 - PL/Python procedural language for PostgreSQL 10
 postgresql-plpython3-10 - PL/Python 3 procedural language for PostgreSQL 10
 postgresql-pltcl-10 - PL/Tcl procedural language for PostgreSQL 10
 postgresql-server-dev-10 - development files for PostgreSQL 10 server-side 
programming
Changes:
 postgresql-10 (10.3-1) unstable; urgency=medium
 .
   * New upstream version.
 .
 If you run an installation in which not all users are mutually
 trusting, or if you maintain an application or extension that is
 intended for use in arbitrary situations, it is strongly recommended
 that you read the documentation changes described in the first changelog
 entry below, and take suitable steps to ensure that your installation or
 code is secure.
 .
 Also, the changes described in the second changelog entry below may
 cause functions used in index expressions or materialized views to fail
 during auto-analyze, or when reloading from a dump.  After upgrading,
 monitor the server logs for such problems, and fix affected functions.
 .
 + Document how to configure installations and applications to guard
   against search-path-dependent trojan-horse attacks from other users
 .
   Using a search_path setting that includes any schemas writable by a
   hostile user enables that user to capture control of queries and then
   run arbitrary SQL code with the permissions of the attacked user.  While
   it is possible to write queries that are proof against such hijacking,
   it is notationally tedious, and it's very easy to overlook holes.
   Therefore, we now recommend configurations in which no untrusted schemas
   appear in one's search path.
   (CVE-2018-1058)
 .
 + Avoid use of insecure search_path settings in pg_dump and other client
   programs
 .
   pg_dump, pg_upgrade, vacuumdb and other PostgreSQL-provided applications
   were themselves vulnerable to the type of hijacking described in the
   previous changelog entry; since these applications are commonly run by
   superusers, they present particularly attractive targets.  To make them
   secure whether or not the installation as a whole has been secured,
   modify them to include only the pg_catalog schema in their search_path
   settings. Autovacuum worker processes now do the same, as well.
 .
   In cases where user-provided functions are indirectly executed by these
   programs -- for example, user-provided functions in index expressions --
   the tighter search_path may result in errors, which will need to be
   corrected by adjusting those user-provided functions to not assume
   anything about what search path they are invoked under.  That has always
   been good practice, but now it will be necessary for correct behavior.
   (CVE-2018-1058)
Checksums-Sha1:
 f9eee194b9833f22656e8227bc7f2d938021384f 3474 postgresql-10_10.3-1.dsc
 93882ad46aa15fd45bfa53cb7f6532c3070d6964 19959653 
postgresql-10_10.3.orig.tar.bz2
 7ece926244c9a28f39d5a8175de57adcd4c13eb8 22800 
postgresql-10_10.3-1.debian.tar.xz
 fe681168597a63d1b7d32b451ac2f2dc7e48ad4f 8193 
postgresql-10_10.3-1_source.buildinfo
Checksums-Sha256:
 4d1c2d805241ffe873483c66fa531eac1cd785a6dbcfb452e38591abea5d24c7 3474 
postgresql-10_10.3-1.dsc
 6ea268780ee35e88c65cdb0af7955ad90b7d0ef34573867f223f14e43467931a 19959653 
postgresql-10_10.3.orig.tar.bz2
 5349970dd7c757b7dfcaec64d39bc457f15afd65f2307c976a3ce868b49c59bd 22800 
postgresql-10_10.3-1.debian.tar.xz
 1ce988a6632db9d3837b7f38e1176801dbeff3ba8d1fcfcba5c3dd779b36ef31 8193 
postgresql-10_10.3-1_source.buildinfo
Files:
 50cc830c2b22618ff645db6b3a78af43 3474 database optional 
postgresql-1

[Pkg-postgresql-public] Accepted postgresql-9.6 9.6.7-0+deb9u1 (source) into proposed-updates->stable-new, proposed-updates

[Christoph Berg]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Feb 2018 15:01:25 +0100
Source: postgresql-9.6
Binary: libpq-dev libpq5 libecpg6 libecpg-dev libecpg-compat3 libpgtypes3 
postgresql-9.6 postgresql-9.6-dbg postgresql-client-9.6 
postgresql-server-dev-9.6 postgresql-doc-9.6 postgresql-contrib-9.6 
postgresql-plperl-9.6 postgresql-plpython-9.6 postgresql-plpython3-9.6 
postgresql-pltcl-9.6
Architecture: source
Version: 9.6.7-0+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 
<pkg-postgresql-public@lists.alioth.debian.org>
Changed-By: Christoph Berg <christoph.b...@credativ.de>
Description:
 libecpg-compat3 - older version of run-time library for ECPG programs
 libecpg-dev - development files for ECPG (Embedded PostgreSQL for C)
 libecpg6   - run-time library for ECPG programs
 libpgtypes3 - shared library libpgtypes for PostgreSQL 9.6
 libpq-dev  - header files for libpq5 (PostgreSQL library)
 libpq5 - PostgreSQL C client library
 postgresql-9.6 - object-relational SQL database, version 9.6 server
 postgresql-9.6-dbg - debug symbols for postgresql-9.6
 postgresql-client-9.6 - front-end programs for PostgreSQL 9.6
 postgresql-contrib-9.6 - additional facilities for PostgreSQL
 postgresql-doc-9.6 - documentation for the PostgreSQL database management 
system
 postgresql-plperl-9.6 - PL/Perl procedural language for PostgreSQL 9.6
 postgresql-plpython-9.6 - PL/Python procedural language for PostgreSQL 9.6
 postgresql-plpython3-9.6 - PL/Python 3 procedural language for PostgreSQL 9.6
 postgresql-pltcl-9.6 - PL/Tcl procedural language for PostgreSQL 9.6
 postgresql-server-dev-9.6 - development files for PostgreSQL 9.6 server-side 
programming
Changes:
 postgresql-9.6 (9.6.7-0+deb9u1) stretch; urgency=medium
 .
   * New upstream version.
 + Ensure that all temporary files made by pg_upgrade are
   non-world-readable (CVE-2018-1053)
 .
 + Change the behavior of contrib/cube's cube ~> int operator to make it
   compatible with KNN search.
 .
   The meaning of the second argument (the dimension selector) has been
   changed to make it predictable which value is selected even when
   dealing with cubes of varying dimensionalities.
 .
   This is an incompatible change, but since the point of the operator
   was to be used in KNN searches, it seems rather useless as-is.
   After installing this update, any expression indexes or materialized
   views using this operator will need to be reindexed/refreshed.
Checksums-Sha1:
 98350531051420c1217efff2eeda3bc57ef4cd6e 3694 postgresql-9.6_9.6.7-0+deb9u1.dsc
 cac19c1c688aeaae0eacad7879a301fda4c72fb3 19504886 
postgresql-9.6_9.6.7.orig.tar.bz2
 7e94c1720e50c565b48ed6da5863003ae19f8ccc 21952 
postgresql-9.6_9.6.7-0+deb9u1.debian.tar.xz
 5784afbae74bf911adb29b3e1fdc0fb5d74a8a7c 8653 
postgresql-9.6_9.6.7-0+deb9u1_source.buildinfo
Checksums-Sha256:
 3d1ca1170816e070ad45c11d04b5dac2c0a2b5662d6e23af3cb2a7e8dba29877 3694 
postgresql-9.6_9.6.7-0+deb9u1.dsc
 2ebe3df3c1d1eab78023bdc3ffa55a154aa84300416b075ef996598d78a624c6 19504886 
postgresql-9.6_9.6.7.orig.tar.bz2
 18085bd8ecd2251c1600bbd50f5e7b4e8b0f91ee2bc652882c30042995fab63d 21952 
postgresql-9.6_9.6.7-0+deb9u1.debian.tar.xz
 09c59f2e45f4beaab09ad051e12b7f433b77b93975c208d8d41d5f9b795cb6cd 8653 
postgresql-9.6_9.6.7-0+deb9u1_source.buildinfo
Files:
 6a228cd4f71c3e83498ff503b98acb12 3694 database optional 
postgresql-9.6_9.6.7-0+deb9u1.dsc
 46c1593be57c1122c0313193ad2b9891 19504886 database optional 
postgresql-9.6_9.6.7.orig.tar.bz2
 98ace4c5f11552ced53196a1121ca393 21952 database optional 
postgresql-9.6_9.6.7-0+deb9u1.debian.tar.xz
 92928a0d9dbb34d442ce0ddadc856227 8653 database optional 
postgresql-9.6_9.6.7-0+deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlp8E8AACgkQTFprqxLS
p65hnhAAmGVafnohBdhWc0u0YCRJ9ESCaZ/MW/pfRXlNx8axIh1USIlxT+DDoSIG
PoQy72K6r58T/kuLATVciopGIT1tbIWBU26MBxMGXFty16Wa5GKu9oYSi3Y0eE0c
PYddhEjdlUWVEkrrgFNfREolqTZgRxaU+QE4P2fDO/1E9krFolyfqSzsq/ZFrVfd
LUrdZOnSsB6zTOokyrttmNcC5rDoiXimSm3wCMlDmlP6Fev833T1zIMy7uLIhqW6
eVR2uYGqBFLxnbz8VscDmRV7BsG1p5uVXZ1T77QhAIBY+MqgK5WkIsgaW/Dgr9tY
UBFxnosv19g4a5mvnuD2Fhsd+ECAxBCmbIsscebSviGpOF8CtulC1CDTMvkajK5i
ReKGJD/uqeG9Uq+x1bK8bTKVFN4qi/Zz0jKLpF354ur5JDByjPRyh89B6sDSU/pQ
Z4sV8zwhvzuiAuczdDwoF7eGfaFyu6IWsHV1NLuxNewR0urO7D6w7NvbQ56Y2m7p
nMKl6IYaI2Oh9zNj63h0SjqJN8++ldz8L+jfsr+mihXs1YHWBJOOtsWEuv+kD2nX
LFoxQZvLjg0OVwm/yRLJb1rkWc2kjzH/wwkPXAVObyR30FscU/emcspisFZsEtqb
N/PeG9yscze7R+KNcjNV70oyLZ29iIk1uiyogmMookOqCABh/GY=
=IjRw
-END PGP SIGNATURE-


___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#891049: pgmodeler: version in stretch incompatible with db version in stretch

[Christoph Berg]

Control: severity -1 serious
Version: 0.9.1~beta-1

Re: Toni Mueller 2018-02-21 
<151925212500.8837.9009431344134188619.report...@spruce.office.oeko.net>
> I would like to use pgmodeler in Stretch, but the program can't work
> with PostgreSQL 9.6, also in Stretch. I get an error message that only
> versions up to 9.5 are supported, and that's the end of the story.

Oops.

We've only recently imported pgmodeler into the PostgreSQL team, so
obviously this incompatibility fell through the cracks. Sorry.

I don't see that we can realistically upgrade pgmodeler in stretch, so
there's two workarounds available: using pgmodeler from buster, or use
the stretch-pgdg distribution from apt.postgresql.org.

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#890830: Bug#890830: pgmodeler: unable to connect to remote dbcluster with ssl

[Christoph Berg]

Re: Wim Bertels 2018-02-19 
<151905236880.17985.13240849843143808872.report...@lolifant.intranet.ucll.be>
> Package: pgmodeler
> Version: 0.8.2-1.pgdg90+1
> Severity: normal
> 
> Hallo,
> 
> i'm unable to add a new working connection to pgmodeler
> 
> use case:
> host: remote host
> port: non standard
> sslmode : require

Hi Wim,

I couldn't get a working SSL connection with 0.8.2 either. I've now
promoted the new 0.9.1~beta version on apt.postgresql.org where it
works. (The connection edit dialog is still pretty fragile, lots of
buttons, unclear where one has to click.)

Does that fix the problem for you?

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#749809: pgpool2: Undefined conversion from double to enum

[Christoph Berg]

Control: tags -1 moreinfo

Re: Michael Tautschnig 2014-05-29 <20140529213909.gh1...@l04.home>
> Package: pgpool2
> Version: 3.3.3-2
> Usertags: goto-cc
> 
> During a rebuild of all packages in a clean sid chroot (and 
> cowbuilder+pbuilder)
> the build failed with the following error. Please note that we use our 
> research
> compiler tool-chain (using tools from the cbmc package), which permits 
> extended
> reporting on type inconsistencies at link time.

Hi Michael,

is this problem still present?

> [...]
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -D_GNU_SOURCE -I .. -I 
> /usr/include/postgresql -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector 
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall 
> -Wmissing-prototypes -Wmissing-declarations -MT pcp.lo -MD -MP -MF 
> .deps/pcp.Tpo -c pcp.c  -fPIC -DPIC -o .libs/pcp.o
> file pcp.c line 1649 function pcp_watchdog_info: in expression `atof(index)':
> conversion from `double' to `WD_STATUS': implicit conversion not permitted
> CONVERSION ERROR
> Makefile:638: recipe for target 'pcp.lo' failed
> make[3]: *** [pcp.lo] Error 1
> make[3]: Leaving directory 
> '/srv/jenkins-slave/workspace/sid-goto-cc-pgpool2/pgpool2-3.3.3/pcp'
> Makefile:861: recipe for target 'all-recursive' failed
> make[2]: *** [all-recursive] Error 1
> 
> This is here:
> 
> http://sources.debian.net/src/pgpool2/3.3.3-2/pcp/pcp.c?hl=1649#L1649
> 
> It may have historic reasons that atof is used here, but this should really 
> be a
> checked conversion towards one of the legitimated values of WD_STATUS:
> 
> http://sources.debian.net/src/pgpool2/3.3.3-2/watchdog/watchdog.h?hl=109#L103
> 
> (and that checked conversion would use atoi).

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Accepted pspg 0.9.3-1 (source) into unstable

[Christoph Berg]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 15 Feb 2018 10:18:02 +0100
Source: pspg
Binary: pspg
Architecture: source
Version: 0.9.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 
<pkg-postgresql-public@lists.alioth.debian.org>
Changed-By: Christoph Berg <m...@debian.org>
Description:
 pspg   - PostgreSQL pager
Changes:
 pspg (0.9.3-1) unstable; urgency=medium
 .
   * New upstream version.
Checksums-Sha1:
 ba241b28014898620593d3e064408aa7c3f73beb 1983 pspg_0.9.3-1.dsc
 a7d93c144267522193f7a1cf3ffc945bac716289 856766 pspg_0.9.3.orig.tar.gz
 87a09e16af93cb6b6524eeb9ee84723dc0651cd5 2468 pspg_0.9.3-1.debian.tar.xz
 2075c8b228a921871ed3bd4849787f96e33be112 5286 pspg_0.9.3-1_source.buildinfo
Checksums-Sha256:
 b129dae6a1a0790dbb1c6454793d3fb792c32b5019b1dbff469d645ff482cc27 1983 
pspg_0.9.3-1.dsc
 399a9baa4cf92f6ba5248e4a1509dfd4a1ca09132aa439b8d8c0e17396eae94c 856766 
pspg_0.9.3.orig.tar.gz
 2ed8a5f6c914f3706f746bbe57f576349e4051d66cb0ca92054849705b6374c3 2468 
pspg_0.9.3-1.debian.tar.xz
 6c2517317cb6193761f4702944fe75d45c1c22cd0b16d9961064975bcd897d0c 5286 
pspg_0.9.3-1_source.buildinfo
Files:
 33f4866f646a132b2311621af17f7756 1983 database optional pspg_0.9.3-1.dsc
 290f84534a21cb195e191b8a29d5459b 856766 database optional 
pspg_0.9.3.orig.tar.gz
 7e10fc88027384de4bcd4d8560d51eb0 2468 database optional 
pspg_0.9.3-1.debian.tar.xz
 852dd8d8c289d6cdf29e5b231d6082b2 5286 database optional 
pspg_0.9.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlqFUUgACgkQTFprqxLS
p64VRQ/+PvyxZMvmx5kwdKJXxbaZ7D07ME1ws9UNA3BBRFIeLORTVLpZhGxtNCOn
AZjmYLP6U8psEvGZp4Nr9NM+DQYbYNKqkPOcaH+nki+eq72+3bdNhKHDsW9lOXdH
OEILS1H8vROQ8ZnNTBtURldW8vXDt1Ay4RuVDkzu3H41XNdHRjKacukhFGxItdNn
1615RKh9227gFoTKh5BWBf2hKy0+n+29MlFZoJve5XEXA7lOTncRT5wyGXd8JybA
sfJA1baY6rEgGyyoU99Mo3ZrPnrQqU3MY7URBnfps6Bb3jgeeEXjvnORHKNEDREB
1hetq75MAWBlaekFuWEI5eZ3erkUuHr6BJ9eF2yYe6DS0aSJTahUCXeGpBcpAZKS
MGYXM96Om/m61clToqAZVG9ScDJep41zP7rtjYTXg/THgRcgbxsKTE6YIRj/dIrU
xCFfIBzuyLEiujpCkwkZnDzyJJyxB/HHfWL01eMTCSo1r4AneVofkss6nEAU51cZ
mY5mm3e0Xo3Y0rjOYt/YiEHE1OMQ/YiULFGwX81rNsvmxMteKnWhqH6Bhed4d0NF
iCpbQPgCINv8ASrbSelAlDOVAwvosDMLl89AOnkl/LsxyccsSob6cGBvEm7OOA/W
Bd/CN+7PQqeJMUzmOvc5gZcmh+gOankAQF/pmNq9K6I+IVUgKiY=
=9/lg
-END PGP SIGNATURE-


___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] python-skytools_3.3-1_amd64.changes REJECTED

[Christoph Berg]

Re: Thorsten Alteholz 2018-02-13 
> please mention
>  python-skytools/skytools/apipkg.py
> in your debian/copyright.

Hi,

done now. Thanks for spotting!

Christoph
-- 
Senior Berater, Tel.: +49 2166 9901 187
credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209
Trompeterallee 108, 41189 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer
pgp fingerprint: 5C48 FE61 57F4 9179 5970  87C6 4C5A 6BAB 12D2 A7AE


signature.asc
Description: PGP signature
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Accepted pgadmin3 1.22.2-4 (source) into unstable

[Christoph Berg]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 11 Feb 2018 20:50:47 +0100
Source: pgadmin3
Binary: pgadmin3 pgadmin3-data
Architecture: source
Version: 1.22.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 
<pkg-postgresql-public@lists.alioth.debian.org>
Changed-By: Christoph Berg <m...@debian.org>
Description:
 pgadmin3   - graphical administration tool for PostgreSQL
 pgadmin3-data - graphical administration tool for PostgreSQL - documentation
Closes: 878295 888421
Changes:
 pgadmin3 (1.22.2-4) unstable; urgency=medium
 .
   * Move packaging repository to salsa.debian.org
   * pgadmin/include/pgAdmin3.h: Don't check for maximally supported PG
 version.
   * Support PG 10: Replace various occurrences of "xlog" by "wal" and
 "location" by "lsn". Patch by Bernhard Rieder and Christoph Berg.
 (Closes: #878295, #888421)
Checksums-Sha1:
 724e95f2a1c7bdcd84bd6c8685a04a23c253a795 2250 pgadmin3_1.22.2-4.dsc
 a0a4f4a5ca5ff8c83e25ee4a9a1eaf8b0c1dcdc3 20324 pgadmin3_1.22.2-4.debian.tar.xz
 7aca6ddf535b8ed48a634109ee88d21d6277061e 12254 
pgadmin3_1.22.2-4_source.buildinfo
Checksums-Sha256:
 0643557a36e1082273f62ba5e973abfa410d56409af41918312549d0ea128c61 2250 
pgadmin3_1.22.2-4.dsc
 003ce27647339acd75818eb6a057b0d7b329121a23ddd523383a825377a593bc 20324 
pgadmin3_1.22.2-4.debian.tar.xz
 1e0e7ef498aa0c89496720b12736fd4ed032aec8968e70de4af301391e1e41cc 12254 
pgadmin3_1.22.2-4_source.buildinfo
Files:
 e19c6aa08642c03d96b10f1001ce7bb4 2250 database optional pgadmin3_1.22.2-4.dsc
 164f9ae843547f665057ee5e264fcdf5 20324 database optional 
pgadmin3_1.22.2-4.debian.tar.xz
 21b71b50045385f2b64e925643ec2319 12254 database optional 
pgadmin3_1.22.2-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlqAoWAACgkQTFprqxLS
p66RQw//aqtp0clXOgv5+OANnnsp+TUNkpO4jVR7VMKQSa1ZnsNCoJYkBNcC9qli
HIX+2VrhMzE4BJLznSwEtYAw+YP19iZG58OjkZA3h9tVXrsnbEHuCDR8j0aGX/Si
ZEajiO99dI77LA/8gEUO+jgiuR5FZA82wxVu1YfYtc5trZn+xKJpspUXbOitGwFn
+5BDTMCwJJyZppXUIBjnr0VsKEbvp15T4vHj4H71XmR5EUwodcW+f2C5uu3bY24i
yOGfBZa8yF++DTAdtPyT88OXVNip6naj8i+xMqP/oyYsxPiGF71Bmf2XfDANeLE9
Wq4tJ+Lc1ZfFUHbfAcUkb11a8fxb/NYr6/2J27XgCfaS8611kJC7voijECGn+MOW
VW445yVPxHH8YlUM5Na+ZpMeMpfBguolTQspz9tuIRdcUJXXLl92+sF61xz3iaUY
Q4VJ49Kl0AAML0QFtORUKNHKpa8xoH3mf5njUdOMkGh7jzMf2YFspDDSGVv0AYCK
+2NfZ+LcI1Nw8cDhrjS+xZVaSqF1R5TfzivLxK8NHCIuMs0+O+W3jOxxoYWLUo0r
6b0/cLmKfeotcmCIfSc1rbD+cGaVtVE8k/qCl+rYM+sHEWSoBDA71C8AekY/wi8s
XD6w2MH5TN+KQMuI6UcEWlwFippR1w59uFn7o4drOJvTZq4fGog=
=jsXm
-END PGP SIGNATURE-


___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Accepted postgresql-common 190 (source) into unstable

[Christoph Berg]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 08 Feb 2018 13:26:44 +0100
Source: postgresql-common
Binary: postgresql-common postgresql-client-common postgresql-server-dev-all 
postgresql postgresql-client postgresql-doc postgresql-contrib postgresql-all
Architecture: source
Version: 190
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 
<pkg-postgresql-public@lists.alioth.debian.org>
Changed-By: Christoph Berg <christoph.b...@credativ.de>
Description:
 postgresql - object-relational SQL database (supported version)
 postgresql-all - metapackage depending on all PostgreSQL server packages
 postgresql-client - front-end programs for PostgreSQL (supported version)
 postgresql-client-common - manager for multiple PostgreSQL client versions
 postgresql-common - PostgreSQL database-cluster manager
 postgresql-contrib - additional facilities for PostgreSQL (supported version)
 postgresql-doc - documentation for the PostgreSQL database management system
 postgresql-server-dev-all - extension build tool for multiple PostgreSQL 
versions
Closes: 887251
Changes:
 postgresql-common (190) unstable; urgency=medium
 .
   * Move packaging repository to salsa.debian.org
   * pg_lsclusters: Add --help.
   * pg_virtualenv: Error out if no server packages are installed.
   * postgresql-common recommends e2fsprogs, we are using chattr in
 pg_createcluster. (Closes: #887251)
   * PgCommon.pm: Fix include directives parser, spotted by ironhalik, thanks!
   * postgresql@.service: Set Timeoutstart=0, which is the same as infinity,
 but works on older systemd versions as well.
   * Rewrite architecture.html as README.md.
   * t/006_next_free_port.t: Drop -q argument from netcat, nmap-ncat.rpm
 doesn't have it.
   * t/032_ssl_key_permissions.t: Adjust for 9.4 in oldstable which still has
 the old permissions check.
Checksums-Sha1:
 8de735103c4fe7dd0c0b293a40a673b1bbb1c9f6 2320 postgresql-common_190.dsc
 521a1729e77c0b5623c8557150110d78c81f1dd1 207608 postgresql-common_190.tar.xz
 a4115e739379ab58e261e9dee2909c39afed6a0e 5921 
postgresql-common_190_source.buildinfo
Checksums-Sha256:
 b07ffdabeab1fa0a327346f6795c8d2df8a57da37035d2df46a1ca8d04306bfd 2320 
postgresql-common_190.dsc
 d6135584845208b798f1346fa982e2d2191a909c9bbe14e509e4d0caf97c6939 207608 
postgresql-common_190.tar.xz
 1f7d0da97b08d6a4b7369ab68bdb3fbb326075a07efe0c23c8cfbde88a920f0b 5921 
postgresql-common_190_source.buildinfo
Files:
 0248ad7d81630fc290ba36676f867dce 2320 database optional 
postgresql-common_190.dsc
 80d8570e96646ffa99876f512bbf4d85 207608 database optional 
postgresql-common_190.tar.xz
 35647ce7816de217d37e73f84cc65675 5921 database optional 
postgresql-common_190_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlp8SBgACgkQTFprqxLS
p66+kw//UQb58QL5Nr+r1sra2Zs7+k8nlZqs6TLR8aVOIrX842IfpQJhV92cC8/R
sD0kCGYZz4kMsaAczkvmHehntgXxwAyZbR2XVnK2NO6ICyRwBI1nKrHwFkNJ0/Fr
3Lc2mEX5+5GxsQhoAZ4wRm3sAWnLValUOuqYWbzFtYVsvMTCMlRsUMTOOBavexUs
2Km7IKsIMa3LpjEJSzxovsstHKTcGdBktk6MbpTsnFtIeu+C6hvWyVtTvrk/+0KP
m7a5NL0tNxibmKHxl3lr0PSMOUqt0YqsF1hK+S9WtfOqlNbHzrQx4y+hwGrV9it1
OGo+O1TSW71BSyazdhgO9Lj5NX9cOghNwM20lbYtmVBaeAcv59jDoqB4ORDZAFVP
Sqb/WAF4Hvu10O6FwjFz8NKcsQCQXkec9f8nLy5rSCzjk26oJW7NCG/KGBYnmX9u
/dq+pVM8F5NrJw8BRn7G4a4XyYznMKGzapNSfV84Pqn+idGGv2O8VB33h7O1uQmm
a5qXTCVXSqxreoshlmokHXHTY+bDCbseORVCQl+KITjOaHh/wsb9twGCAivFi2lH
lT0oMJe/zu4Vogqoj0gLBYIeZI+1/MyhQCIecWvQOoc1Xthu7H0K7/9ap9jNPbCb
+WWK9V2mgjb18+MwzNkJGmYKjv1+2f6iEnAkTzndOSd1M1h6/Eo=
=VBRi
-END PGP SIGNATURE-


___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Accepted postgresql-10 10.2-1 (source) into unstable

[Christoph Berg]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 07 Feb 2018 13:50:31 +0100
Source: postgresql-10
Binary: libpq-dev libpq5 libecpg6 libecpg-dev libecpg-compat3 libpgtypes3 
postgresql-10 postgresql-client-10 postgresql-server-dev-10 postgresql-doc-10 
postgresql-plperl-10 postgresql-plpython-10 postgresql-plpython3-10 
postgresql-pltcl-10
Architecture: source
Version: 10.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 
<pkg-postgresql-public@lists.alioth.debian.org>
Changed-By: Christoph Berg <christoph.b...@credativ.de>
Description:
 libecpg-compat3 - older version of run-time library for ECPG programs
 libecpg-dev - development files for ECPG (Embedded PostgreSQL for C)
 libecpg6   - run-time library for ECPG programs
 libpgtypes3 - shared library libpgtypes for PostgreSQL 10
 libpq-dev  - header files for libpq5 (PostgreSQL library)
 libpq5 - PostgreSQL C client library
 postgresql-10 - object-relational SQL database, version 10 server
 postgresql-client-10 - front-end programs for PostgreSQL 10
 postgresql-doc-10 - documentation for the PostgreSQL database management system
 postgresql-plperl-10 - PL/Perl procedural language for PostgreSQL 10
 postgresql-plpython-10 - PL/Python procedural language for PostgreSQL 10
 postgresql-plpython3-10 - PL/Python 3 procedural language for PostgreSQL 10
 postgresql-pltcl-10 - PL/Tcl procedural language for PostgreSQL 10
 postgresql-server-dev-10 - development files for PostgreSQL 10 server-side 
programming
Changes:
 postgresql-10 (10.2-1) unstable; urgency=medium
 .
   * New upstream version.
 + Fix processing of partition keys containing multiple expressions
   (CVE-2018-1052)
 .
 + Ensure that all temporary files made by pg_upgrade are
   non-world-readable (CVE-2018-1053)
 .
 + Change the behavior of contrib/cube's cube ~> int operator to make it
   compatible with KNN search.
 .
   The meaning of the second argument (the dimension selector) has been
   changed to make it predictable which value is selected even when
   dealing with cubes of varying dimensionalities.
 .
   This is an incompatible change, but since the point of the operator
   was to be used in KNN searches, it seems rather useless as-is.
   After installing this update, any expression indexes or materialized
   views using this operator will need to be reindexed/refreshed.
Checksums-Sha1:
 85385acdd7cf262e8496bfa47ab8c7f7503d48f9 3474 postgresql-10_10.2-1.dsc
 b0597de368dac410cfb65ce92f89e324bbdc1ea1 19901836 
postgresql-10_10.2.orig.tar.bz2
 c08cc9187c3aee9d4961ee5b1c07b0faf8ea9f16 21944 
postgresql-10_10.2-1.debian.tar.xz
 253f8e2226a8e14fad481049a7282b3ff7413c35 8282 
postgresql-10_10.2-1_source.buildinfo
Checksums-Sha256:
 b91226ffd94639ba013cf46fa7d205b1d30c103066da8100c9db8018bf10227f 3474 
postgresql-10_10.2-1.dsc
 fe32009b62ddb97f7f014307ce9d0edb6972f5a698e63cb531088e147d145bad 19901836 
postgresql-10_10.2.orig.tar.bz2
 ea39edbbdc16ec8053f6a378b56e7137ebdd332bd6575d009323ed498991d48d 21944 
postgresql-10_10.2-1.debian.tar.xz
 5e3685eeaacef7bc85174e1573ccb1d075db1332daecf92a9bcc56135b77e0d4 8282 
postgresql-10_10.2-1_source.buildinfo
Files:
 90383cd8fc5194907e320c7088e6b3a6 3474 database optional 
postgresql-10_10.2-1.dsc
 e97c3cc72bdf661441f29069299b260a 19901836 database optional 
postgresql-10_10.2.orig.tar.bz2
 b33bcca4da894b5f2de5073b2bc3d801 21944 database optional 
postgresql-10_10.2-1.debian.tar.xz
 6261cf756a3ceb6fdc80653c9b23eaf5 8282 database optional 
postgresql-10_10.2-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlp8OngACgkQTFprqxLS
p64DeBAAo5fz4YnNeOQKpl1noNos/x3GnJqPJBcYONfU1kJ4xSxxzFjMgx1YcQN0
utE268PuJG3jFSDMULmODf6E3Ak1H67r096RynR0pXGEf9OhW6P3LDX14E5FwNMQ
VF82IVWmtVM8p6/uqMgNNtxpONQxtJjgr2NN5jfkVSf8fbfGayqAjx+/RgdkRMqP
KraT9OJ3nnDohnROgJDRQCQ8+OIukP7VoL+C6ZpO+yG0rS4AbWSGpCI7O6pvaCCj
3MabUbaEh5LNWghikfTpCcEKUdjUUXhXbywL42Efwccj0qaP6R0Fke4IAS6Y+iIC
QhG3pBS91wj1lvWXMXLFhlRXRa47SLlVYYHOuCVNNPSAsw2xFOtddusEBd2N6RPY
WuDWhJQtq7PeIskU78T7IdHtgJ8kXNE3J99gPJjzCh7cv42+KrpFJiaVMrQz/WsR
es1i22UaT391SfCKdsrogSC486BSiAuXDxK+T8zZzaMtzp98s/r2tacYmupSSV/B
9WchiNuSYvkKbApSSZFiZMKE3lK9zc7VlhpJI1bl02+HqBNtAwra9qn+bj2GCR02
g6ujFiaHmBTSWvk36GARqtp25P43N7brnOUTgjh8J1dPMCoTU3Ultg5VQHDs6Mol
V0Nbsjt4TxkjaTteCK+B0XkYp9BGcyGQAXomOJ7/SueTLcGenbY=
=Y2ZX
-END PGP SIGNATURE-


___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] Debian Stretch armhf PostgreSQL package

[Christoph Berg]

Hi,

Re: Ertan Küçükoğlu 2018-02-06 <01d39f0e$79bcef20$6d36cd60$@1nar.com.tr>
> My questions are:
> 1) What version of openssl library above postgresql package compiled with?

libssl1.1 (= 1.1.0f-3+deb9u1)

> 2) Is there any new upgrade of PostgreSQL package that will be released
> soon?

There will be new minor releases on Thursday this week, including some
security fixes, so there will be a stretch update as well.

> 3) If PostgreSQL compiled with a different openssl version than
> openssl/stable, will it be same openssl version for next upgrade of
> PostgreSQL?
> 4) Is there a way for me to verify that my problem is really because of
> different openssl versions? 

Note that the problem in that stackexchange post was due to
mismatching signature algorithms in the certificate. SHA1 has been
deprecated and modern SSL libs reject certificates using it. I'd start
by verifying that:

openssl x509 -text < server.crt

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Accepted prefix 1.2.7-1 (source) into unstable

[Christoph Berg]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 05 Feb 2018 15:11:51 +0100
Source: prefix
Binary: postgresql-10-prefix
Architecture: source
Version: 1.2.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 
<pkg-postgresql-public@lists.alioth.debian.org>
Changed-By: Christoph Berg <christoph.b...@credativ.de>
Description:
 postgresql-10-prefix - Prefix Range module for PostgreSQL
Changes:
 prefix (1.2.7-1) unstable; urgency=medium
 .
   * New upstream version, removing support for 8.x and fixing compatibility
 with 10.x.
Checksums-Sha1:
 503d0434af4b9f516c2769ddbd54c480cf423dbd 2000 prefix_1.2.7-1.dsc
 754fbe48defa6c9626a58bc37c84cc5b3f011b29 71812 prefix_1.2.7.orig.tar.gz
 0f2b7d862cfba559b2d22a84c2723c44220bf071 3796 prefix_1.2.7-1.debian.tar.xz
 7e4a258663a6eb507daa3eb39b45f01bca31a2db 7250 prefix_1.2.7-1_source.buildinfo
Checksums-Sha256:
 820ce9016db40783973238fc8321296bf16a8a195398614ee1b131a435d007ed 2000 
prefix_1.2.7-1.dsc
 294f4a3af2cbe95db5e437666f2001a4f390c0a93828d080dd7375cfbf14a5e9 71812 
prefix_1.2.7.orig.tar.gz
 38d7a385f77b23278872e90c826849b25c38c8202314d90e1116bc42780fd5ab 3796 
prefix_1.2.7-1.debian.tar.xz
 9c4503055dce925182d4565b4ff80effc08d26c92e2c681a3613063316365849 7250 
prefix_1.2.7-1_source.buildinfo
Files:
 fe015e19668f8c393ff694e1f2ecc2a0 2000 database optional prefix_1.2.7-1.dsc
 23877d6a89339650d94ed870bc930d1e 71812 database optional 
prefix_1.2.7.orig.tar.gz
 e97e2af8e14ee535dcda4db22f6ed8cd 3796 database optional 
prefix_1.2.7-1.debian.tar.xz
 947a2e0a1eb08797a6fe52f99542a15c 7250 database optional 
prefix_1.2.7-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAlp4aDgACgkQTFprqxLS
p66rOg//RSOltlbs8D9OJ1cDbGhvG3Je+pa0pxcXPu9tPHYmSMqm9lUqOjxDDVK/
Rk1FqYXCiYvNzr7A5Slm4JE+KY3pwBEdj+8ymt7V1OeGFJC+/nXU/HIC7snXV5ZF
yl8fISGWlAAEUXPue88QLEBw6BpbC6Q7tb4yBuizuD94C/o99S8MerTAmn2Agvhb
AF93VM3QwAC3Ievqw7WQ92x5ZWg9hHOoIcS8yR+fPEyNsUiqt0L3SzXBSKwJc12s
nuPRN1SfQFxTn8HPF1t5PAI54GZSwF9dxwxeB0UoMuJEvtX5NDR40wNeUNLnD/Xa
PKai2oT7yOnqPAqJe/FN1hFHgAtbXTWX57reJVwKAr+pjXiN0qSIswaDxJHkhfvy
X+BJXah66Qe8+bJ4T7sQmlnWMX1XJ0P82IrMGVV9s8yLa7dXLPYpc/CC0dpoUlkz
4FOP4O2W/1NuTLCUYezMPP4LxmPqTokZdj7z055Sa6CuTBC/gAS37h7gDalgFxwU
4KgLFrq7sfdPf4lpWmssJOfyzPpno+AI/C3uFYqMSfV+68VXJc9As4wa0N7F32JS
OALeaY08b9XoHUUymCEqYO28CdyIkW2rTYevV236/OXAfhbWgiIT9f5GjiHcVp8+
4VEMPV6KTYHxVIpz4YcCj5dsk5J+taRylz+t2X9MI8tClv2CMWc=
=eV28
-END PGP SIGNATURE-


___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#887251: postgresql-common should depend on e2fsprogs explicitly

[Christoph Berg]

Re: Andreas Henriksson 2018-01-22 <20180122200302.7di4vjwceuazg...@fatal.se>
> On Sun, Jan 14, 2018 at 08:09:11PM +0100, Helmut Grohne wrote:
> > Package: postgresql-common
> [...]
> > /usr/bin/pg_createcluster contains chattr. According to file it is a Perl 
> > script text executable
> [...]
> 
> For a start I guess it begs to be asked if the users who has
> postgresql-common package installed are likely to ever use the
> pg_createcluster script at all... based on that alone a Depends might
> not be warranted.

postgresql-common is primarily a dependency of the PostgreSQL server
packages, and the server is only useful once pg_createcluster was run
(which happens via the postinst on the first install).

> Looking at the code we'll find the following use of chattr:
> 
> # disable copy-on-write semantics for PostgreSQL data on btrfs and 
> similar;
> # this fails on file systems which don't support it, so ignore errors
> system "chattr +C '$datadir' 2>/dev/null";
> 
> https://sources.debian.org/src/postgresql-common/189/pg_createcluster/#L62
> 
> This doesn't make me feel a dependency is warranted. Possibly a Recommends
> or Suggests. Even just closing this bug report with no action could seem
> like the proper response to me.

Given that a typical install will probably have e2fsprogs installed
anyway, I guess it won't matter much if we chose Recommends or
Suggests here. I'll go with Recommends as that code path is taken for
basically all users, and the result should be predictable.

https://salsa.debian.org/postgresql/postgresql-common/commit/d4a4aaad7cbc0796204f3b8cf66b7e8f26454e54

Thanks!

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#887940: Bug#887940: libpq-dev: changed version format in pg_config causes other packages to FTBFS

[Christoph Berg]

Control: reassign -1 src:libpreludedb

Re: Adrian Bunk 2018-01-23 <20180123043023.GA11847@localhost>
> > > ./configure: line 19300: test: too many arguments
> > > ...
> > 
> > Looks like the ax_lib_postgresql.m4 macro should be fixed with some
> > additional shell quoting.
> 
> This is not about quoting, the pg_config output changed:
> 
> 10.1-3:
> $ pg_config --version
> PostgreSQL 10.1 (Debian 10.1-3)

The macro is buggy anyway, it decomposes the string into
major/minor/micro, but the middle component doesn't exist anymore with
PostgreSQL 10. That was fine with 10.0, but with 10.1, it will think
there was a new major release "10.1".

Both issues need to be fixed on the libpreludedb side.

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] bug in the export feature of phpPgAdmin

[Christoph Berg]

Re: roger21 2018-01-06 <92bd5665-a16a-c29c-2d82-8b01ecc14...@free.fr>
> Hi,
> 
> i can't do a descent bug report but still i'm trying to report that :
> 
> the export feature of phpPgAdmin fails since it uses an obsolete parameter
> (-i) for pg_dump as reported by the apache/php error log :
> 
> 
> error.log:/usr/lib/postgresql/9.6/bin/pg_dump: invalid option -- 'i'
> error.log:Try "pg_dump --help" for more information.

Hi Roger,

I opened a bug for this: https://bugs.debian.org/886454

> the phpPgAdmin development seems discontinued but i hope this could be
> patched since it is so minor.

Aye.

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] Pgpool2 3.7.0 availablility

[Christoph Berg]

Re: tiago jose 2017-12-14 

[Pkg-postgresql-public] Bug#882409: Bug#882409: postgresql-9.4: jessie->wheezy on amd64: psql: FATAL: Peer authentication failed for user "postgres"

[Christoph Berg]

Control: severity -1 important
Control: forwarded -1 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710275

Re: Andreas Beckmann 2017-11-22 
<151135388654.32074.1968724866017892274.report...@zam581.zam.kfa-juelich.de>
>   Upgrading PostgreSQL Cluster from 9.1 to 9.4
>   psql: FATAL:  Peer authentication failed for user "postgres"

Hi Andreas,

this is #710275 which has been fixed in glibc in unstable/testing now.
(Unfortunately I only recently forwarded it to glibc.)

I'm downgrading to important because a simple restart of the
PostgreSQL cluster fixes it.

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#827384: skytools3: please make the build reproducible

[Christoph Berg]

Re: Sascha Steinbiss 2016-06-15 
<146600227630.30651.1401246229844835464.report...@vagrant-debian.vagrantup.com>
> Source: skytools3
> Severity: wishlist
> Tags: patch
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: timestamps fileordering
> 
> Hi!
> 
> While working on the “reproducible builds” effort [1], we have noticed
> that skytools3 could not be built reproducibly.
> 
> The attached patch removes extra timestamps from the documentation generated
> by Asciidoc and Epydoc and also ensure a stable file order when linking object
> files into executables. 

Hi Sascha,

skytools3 is being removed from Debian now, but I've added your patch
to git so it doesn't get lost. We are porting parts of the package to
other source packages, so we might be able to make good use of it.
Thanks!

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#883010: RM: postgresql-9.6 -- ROM; Replaced by postgresql-10

[Christoph Berg]

Package: ftp.debian.org
Severity: normal

Please remove postgresql-9.6, it has been replaced by postgresql-10.
The only reverse dependency at this point is skytools3, which is being
removed via #882611.

Thanks,
Christoph


signature.asc
Description: PGP signature
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] Comments regarding pg-similarity_1.0~20160916-1_amd64.changes

[Christoph Berg]

Re: Thorsten Alteholz 2017-11-26 
> Hi Christoph,
> 
> I marked the package for accept, but you should rather name the license BSD 
> instead of MIT ...

Fixed in git, thanks!

Christoph


signature.asc
Description: PGP signature
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#881498: Bug#881498: postgresql-mysql-fdw: autopkgtests fail with postgresql-10

[Christoph Berg]

Re: Jeremy Bicha 2017-11-12 

> The autopkgtests for postgresql-mysql-fdw started failing once
> postgresql-10 was used by default.
> 
> https://ci.debian.net/packages/p/postgresql-mysql-fdw/unstable/amd64/
> http://autopkgtest.ubuntu.com/packages/p/postgresql-mysql-fdw

I've reported that upstream: 
https://github.com/EnterpriseDB/mysql_fdw/issues/147

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#877982: postgresql-server-dev-10 should depend on libicu-dev et al

[Christoph Berg]

> What software were you trying to compile when you noticed the problem?

https://github.com/akorotkov/vgram
https://github.com/akorotkov/vgram/issues/1

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#710275: postgresql needs restart on libc upgrade

[Christoph Berg]

Control: severity -1 normal
Control: retitle -1 postgresql needs restart on libc/nss upgrade
Control: reassign -1 libc6
Control: affects -1 postgresql-common

Re: To Matthew Gabeler-Lee 2013-12-18 <20131218164859.ge22...@msgid.df7cb.de>
> I've just tried the upgrade, and it is also there with "peer"
> authentication because that also goes through nss, so it has the same
> problem as the usual "pam upgrade needs to restart services":

> (base-wheezy-amd64.cow)root@pgdgbuild:/# sudo -u postgres psql
> psql: FATAL:  Peer authentication failed for user "postgres"
> 
> (base-wheezy-amd64.cow)root@pgdgbuild:/# cat 
> /var/log/postgresql/postgresql-9.1-main.log
> ...
> 2013-12-18 16:42:47 UTC LOG:  local user with ID 101 does not exist
> 2013-12-18 16:42:47 UTC FATAL:  Peer authentication failed for user "postgres"

I've finally taken a closer look at the situation here. There is code
in libc6:amd64.preinst to restart services on upgrade, but I believe
the check is incomplete because it requires "postgresql" to be
installed, while the actual server package is called postgresql-9.6,
postgresql-10, etc. (the "postgresql" meta package is optional):

check="kdm postgresql xdm"
# NSS services check:
echo -n "Checking for services that may need to be 
restarted..."
# Only get the ones that are installed, and configured
check=$(dpkg -s $check 2> /dev/null | egrep '^Package:|^Status:' | 
awk '{if ($1 ~ /^Package:/) { package=$2 } else if ($0 ~ /^Status: .* 
installed$/) { print package }}')
# some init scripts don't match the package names
check=$(echo $check | \
sed -e's/\bapache2.2-common\b/apache2/g' \
-e's/\bat\b/atd/g' \
-e's/\bdovecot-common\b/dovecot/g' \
-e's/\bexim4-base\b/exim4/g' \
-e's/\blpr\b/lpd/g' \
-e's/\blpr-ppd\b/lpd-ppd/g' \
-e's/\bmysql-server\b/mysql/g' \
-e's/\bsasl2-bin\b/saslauthd/g' \
)

What should work is to check for "postgresql-common" to be installed,
and then map the init script name back to "postgresql". This is what
libpam0g does, see libpam0g:amd64.postinst.

libc maintainers: could you implement that?

Thanks,
Christoph


signature.asc
Description: PGP signature
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#878852: Remove postgresql-9.6 from testing

[Christoph Berg]

Re: To Debian Bug Tracking System 2017-10-17 
<20171017091121.565iurh4mohq7...@msg.df7cb.de>
> There's a few dependencies that are updated in unstable, but have not
> transitioned yet:
>   postgresql-mysql-fdw
>   orafce
>   postgresql-pllua
> 
> Waiting for NEW processing:
>   pgextwlist

pgextwlist has just passed NEW, so would need an urgency bump as well.

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#878852: Remove postgresql-9.6 from testing

[Christoph Berg]

Package: postgresql-9.6
Version: 9.6.5-1
Severity: serious

postgresql-9.6 is being replaced by postgresql-10, it can already be
removed from testing.

There's a few dependencies that are updated in unstable, but have not
transitioned yet:
  postgresql-mysql-fdw
  orafce
  postgresql-pllua

Waiting for NEW processing:
  pgextwlist

Fixed in experimental:
  repmgr

Unfixed, but in the works:
  skytools3

Release team:
For the unblocking the python3.6-as-default transition, please
consider removing postgresql-9.6 pgextwlist repmgr skytools3 from
testing, and speeding up the transition of postgresql-mysql-fdw orafce 
postgresql-pllua

Thanks,
Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#878440: RM: pgextwlist -- ROM; no support for PostgreSQL 10

[Christoph Berg]

Package: ftp.debian.org
Severity: normal

Please remove pgextwlist. The package does not support PostgreSQL 10,
and getting it fixed upstream seems unlikely.

Christoph


signature.asc
Description: PGP signature
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#878295: pgadmin3 changes for PG10

[Christoph Berg]

Package: pgadmin3
Version: 1.22.2-1

- Forwarded message from Bernhard Rieder  -

Date: Wed, 11 Oct 2017 16:10:53 +0200
From: Bernhard Rieder 
To: christoph.b...@credativ.de
Subject: pgadmin3 anpassungen für PG10
diff -ur pgadmin3-1.22.2/pgadmin/include/pgAdmin3.h pgadmin3-1.22.2-PG10/pgadmin/include/pgAdmin3.h
--- pgadmin3-1.22.2/pgadmin/include/pgAdmin3.h	2016-11-10 15:13:28.0 +0100
+++ pgadmin3-1.22.2-PG10/pgadmin/include/pgAdmin3.h	2017-10-11 14:40:38.835409091 +0200
@@ -58,8 +58,8 @@
 // Supported server minimum and maximum values.
 const short SERVER_MIN_VERSION_N = 0x0804;
 const wxString SERVER_MIN_VERSION_T = wxT("8.4");
-const short SERVER_MAX_VERSION_N = 0x0906;
-const wxString SERVER_MAX_VERSION_T = wxT("9.6");
+const short SERVER_MAX_VERSION_N = 0x0A00;
+const wxString SERVER_MAX_VERSION_T = wxT("10.0");
 
 // Supported Greenplum Database and Greenplum HAWQ minimum and maximum values.
 const short GP_MIN_VERSION_N = 0x0802;
diff -ur pgadmin3-1.22.2/pgadmin/schema/pgServer.cpp pgadmin3-1.22.2-PG10/pgadmin/schema/pgServer.cpp
--- pgadmin3-1.22.2/pgadmin/schema/pgServer.cpp	2016-02-08 11:25:13.0 +0100
+++ pgadmin3-1.22.2-PG10/pgadmin/schema/pgServer.cpp	2017-10-11 14:55:57.274751845 +0200
@@ -905,13 +905,24 @@
 		if (conn->BackendMinimumVersion(8, 5))
 		{
 			sql += wxT(", CASE WHEN usesuper THEN pg_is_in_recovery() ELSE NULL END as inrecovery");
-			sql += wxT(", CASE WHEN usesuper THEN pg_last_xlog_receive_location() ELSE NULL END as receiveloc");
-			sql += wxT(", CASE WHEN usesuper THEN pg_last_xlog_replay_location() ELSE NULL END as replayloc");
+			if (conn->BackendMinimumVersion(10, 0))
+			{
+sql += wxT(", CASE WHEN usesuper THEN pg_last_wal_receive_lsn() ELSE NULL END as receiveloc");
+sql += wxT(", CASE WHEN usesuper THEN pg_last_wal_replay_lsn() ELSE NULL END as replayloc");
+			}
+			else
+			{
+			sql += wxT(", CASE WHEN usesuper THEN pg_last_xlog_receive_location() ELSE NULL END as receiveloc");
+			sql += wxT(", CASE WHEN usesuper THEN pg_last_xlog_replay_location() ELSE NULL END as replayloc");
+		}
 		}
 		if (conn->BackendMinimumVersion(9, 1))
 		{
 			sql += wxT(", CASE WHEN usesuper THEN pg_last_xact_replay_timestamp() ELSE NULL END as replay_timestamp");
-			sql += wxT(", CASE WHEN usesuper AND pg_is_in_recovery() THEN pg_is_xlog_replay_paused() ELSE NULL END as isreplaypaused");
+			if (conn->BackendMinimumVersion(10, 0))
+sql += wxT(", CASE WHEN usesuper AND pg_is_in_recovery() THEN pg_is_wal_replay_paused() ELSE NULL END as isreplaypaused");
+			else
+			sql += wxT(", CASE WHEN usesuper AND pg_is_in_recovery() THEN pg_is_xlog_replay_paused() ELSE NULL END as isreplaypaused");
 		}
 
 		pgSet *set = ExecuteSet(sql + wxT("\n  FROM pg_user WHERE usename=current_user"));
@@ -1434,7 +1445,11 @@
 bool pgServer::PauseReplay()
 {
 	SetReplayPaused(true);
-	wxString sql = wxT("SELECT pg_xlog_replay_pause()");
+	wxString sql;
+	if (conn->BackendMinimumVersion(10, 0))
+		sql = wxT("SELECT pg_wal_replay_pause()");
+	else
+		sql = wxT("SELECT pg_xlog_replay_pause()");
 	return conn->ExecuteVoid(sql);
 }
 
@@ -1442,7 +1457,11 @@
 bool pgServer::ResumeReplay()
 {
 	SetReplayPaused(false);
-	wxString sql = wxT("SELECT pg_xlog_replay_resume()");
+	wxString sql;
+	if (conn->BackendMinimumVersion(10, 0))
+		sql = wxT("SELECT pg_wal_replay_resume()");
+	else
+		sql = wxT("SELECT pg_xlog_replay_resume()");
 	return conn->ExecuteVoid(sql);
 }
 
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#878032: postgresql: apt-get purge of 9.4 removed service for 9.6

[Christoph Berg]

Re: Allan Wind 2017-10-09 
<150750016078.4449.15642963813174771842.reportbug@pawan.lifeintegrity.localnet>
> Surprisingly that also stopped my 9.6 instance and the service disappeared:
> disappeared:

Hi,

that's #809811, fixed in version 183. I'll see to get that backported
into the postgresql-common version shipped in stretch (181).

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#877982: postgresql-server-dev-10 should depend on libicu-dev et al

[Christoph Berg]

Package: postgresql-server-dev-10
Version: 10.0-1
--- Begin Message ---
Hello,
It seems that PostgreSQL 10 in your package have been build with ICU
support. But postgresql-server-dev-10 doesn't have ICU devel package in
dependences.

Package: postgresql-server-dev-10
Source: postgresql-10
Version: 10.0-1.pgdg17.04+1
Architecture: amd64
Maintainer: Debian PostgreSQL Maintainers <
pkg-postgresql-public@lists.alioth.debian.org>
Installed-Size: 4870
Depends: libpq-dev (>= 10~~), postgresql-common (>= 142~), libc6 (>= 2.14)
Breaks: postgresql-server-dev-all (<< 181~)
Section: libdevel
Priority: optional

It seems to be wrong. Can you be so kind to add libicu-dev to depentences?
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public--- End Message ---
--- Begin Message ---
Re: Денис Смирнов 2017-10-08 

Re: [Pkg-postgresql-public] postgresql-server-dev-10 ICU support

[Christoph Berg]

Re: Денис Смирнов 2017-10-08 

[Pkg-postgresql-public] Bug#877920: postgresql-common: pg_upgradecluster 9.6 -> 10 fails (locale problem)

[Christoph Berg]

Re: Karsten Hilbert 2017-10-07 
<20171007154607.34udpgu2jxwsr...@hermes.hilbert.loc>
> >  chomp $ctype;
> >  chomp $collate;
> >  print STDERR "$ctype / $collate\n";
> >  return ($ctype, $collate);
> 
> Unfortunately not:
> 
>   root@hermes:~/bin# pg_upgradecluster 9.6 main
>   de_DE.UTF-8 / de_DE.UTF-8
>   0
>   Error: could not get cluster locales

This doesn't match the above code ("0"), did you edit the correct
file?

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#877920: Bug#877920: postgresql-common: pg_upgradecluster 9.6 -> 10 fails (locale problem)

[Christoph Berg]

Re: Karsten Hilbert 2017-10-07 
<20171007154139.bpvnx7477qcyh...@hermes.hilbert.loc>
>   condition: $? which is 0 which is "FALSE"

0 is a program exit code where 0 is true and everything else is false.
So yes, this is inverted logic.

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#877920: Bug#877920: postgresql-common: pg_upgradecluster 9.6 -> 10 fails (locale problem)

[Christoph Berg]

Re: Karsten Hilbert 2017-10-07 
<20171007152609.i4m5zc6yuol4j...@hermes.hilbert.loc>
> > > return ($ctype, $collate) unless $?;
> 
> Actually, isn't this inverted logic ?
> 
> It should return(...) unless $? actually is NOT zero ?

The extracted values should be returned if the last psql call exited
with status 0. (Yes this function isn't the most pretty one. I'm
inclined to rewrite the whole psql handling from scratch...)

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#877920: Bug#877920: postgresql-common: pg_upgradecluster 9.6 -> 10 fails (locale problem)

[Christoph Berg]

Re: Karsten Hilbert 2017-10-07 
<20171007132123.7eqyzz7455f5x...@hermes.hilbert.loc>
>   root@hermes:/usr/share/perl5# pg_upgradecluster 9.6 main
>   de_DE.UTF-8 / de_DE.UTF-8
>   Error: could not get cluster locales

Hmm. At least the uninitialized value warning is gone now.

> I also added a print statement:
> 
> chomp $ctype;
> chomp $collate;
> print STDERR "$ctype / $collate\n";
> return ($ctype, $collate) unless $?;
> return (undef, undef);
> 
> which produces the 
> 
>   de_DE.UTF-8 / de_DE.UTF-8

I wonder why $? is non-zero even if the $collate extraction worked.
Can you check if the upgrade works properly if you remove the
"unless"?

 chomp $ctype;
 chomp $collate;
 print STDERR "$ctype / $collate\n";
 return ($ctype, $collate);

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#877920: Bug#877920: postgresql-common: pg_upgradecluster 9.6 -> 10 fails (locale problem)

[Christoph Berg]

Re: Karsten Hilbert 2017-10-07 
<20171007104018.ax3cv7dwqg4s3...@hermes.hilbert.loc>
> Thanks for your response !

Thanks!

>   postgres@hermes:~$ psql -d template1
>   Ausgabeformat ist »wrapped«.

PgCommon.pm doesn't use 'psql -X' so your (or postgres') .psqlrc might
be getting in the way. Could you try the upgrade again after moving
.psqlrc away, or (better) adding an 'X' to PgCommon.pm lines 935 and
939?

open PSQL, '-|', $psql, '-h', $socketdir, '-p', $port, '-XAtc',
 ^
Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#877920: postgresql-common: pg_upgradecluster 9.6 -> 10 fails (locale problem)

[Christoph Berg]

Control: tags -1 moreinfo

Re: Karsten Hilbert 2017-10-07 
<150737030347.16226.787705667158988632.report...@hermes.hilbert.loc>
>   Use of uninitialized value $ctype in scalar chomp at 
> /usr/share/perl5/PgCommon.pm line 947.
>   Use of uninitialized value $collate in scalar chomp at 
> /usr/share/perl5/PgCommon.pm line 948.
>   Error: could not get cluster locales
>   root@hermes:~/bin#
> 
> Anything else I can provide ?

Hi,

could you provide the output of 'psql -l' for the old cluster?
Also, please run

 SHOW lc_ctype;
 SHOW lc_collate;

in the old cluster's template1 database.

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#877851: Stretch pgpool_setup + pg_md5 path

[Christoph Berg]

Re: Dan Thomson 2017-10-05 
<60efcc70-c233-de4a-8024-5b9d1983e...@astuteinternet.com>
> > Though this has a high probability of being addresses, I did see an
> > issue in a the regular Debian Stretch pgpool2 package, so I figure I'd
> > bring it to your attention just in case.

Hi Dan,

I opened a bug for this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877851

> > Both pgpool_setup and pg_md5 exist in the same package, so I'm thinking
> > that either the path for pg_md5 should be changed to /usr/bin or the
> > script should be edited to /usr/sbin as a quick fix.

Aye, thanks for the report!

Fwiw, the reason this hasn't been spotted so far is because we are
still looking for help maintaining pgpool2 - none of the PostgreSQL
maintainers in Debian is actually using the package, so we haven't
stumbled over that yet. (https://bugs.debian.org/772047)

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#877851: pgpool_setup + pg_md5 path

[Christoph Berg]

Package: pgpool2
Version: 3.6.1-1
--- Begin Message ---

Hi everyone,

Though this has a high probability of being addresses, I did see an 
issue in a the regular Debian Stretch pgpool2 package, so I figure I'd 
bring it to your attention just in case.


I was playing with running the pgpool_setup script as I'm just figuring 
things out, and I noticed that pgpool_setup (a bash script) tries some 
non-Debian paths when trying to find binaries, but you can set a bunch 
of environment variables to fix all of these issues, except one: 
pgpool_setup looks to $PGPOOL_INSTALL_DIR/bin (PGPOOL_INSTALL_DIR being 
the install path, eg /usr, /usr/local, etc) for a "pg_md5" binary that 
gets installed in /usr/sbin.


Both pgpool_setup and pg_md5 exist in the same package, so I'm thinking 
that either the path for pg_md5 should be changed to /usr/bin or the 
script should be edited to /usr/sbin as a quick fix.


Anyway, this obviously easy to deal with on my end, but since this issue 
seems to exist in the stable Debian package, I thought I'd mention it.


--

Dan Thomson
d...@astuteinternet.com

Astute Internet Incorporated
T: 1.888.685.1661 (604.637.7939)
F: 604.738.0518
www.astuteinternet.com
100% Uptime Dedicated Hosting in Vancouver, Seattle,
Los Angeles, Toronto, New York and Miami

Follow us on Twitter: @astutehosting


___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

--- End Message ---
--- Begin Message ---

Looks like the same is true for pcp_recovery_node as well as pg_md5.


On 05/10/17 12:23 PM, Dan Thomson wrote:

Hi everyone,

Though this has a high probability of being addresses, I did see an 
issue in a the regular Debian Stretch pgpool2 package, so I figure I'd 
bring it to your attention just in case.


I was playing with running the pgpool_setup script as I'm just 
figuring things out, and I noticed that pgpool_setup (a bash script) 
tries some non-Debian paths when trying to find binaries, but you can 
set a bunch of environment variables to fix all of these issues, 
except one: pgpool_setup looks to $PGPOOL_INSTALL_DIR/bin 
(PGPOOL_INSTALL_DIR being the install path, eg /usr, /usr/local, etc) 
for a "pg_md5" binary that gets installed in /usr/sbin.


Both pgpool_setup and pg_md5 exist in the same package, so I'm 
thinking that either the path for pg_md5 should be changed to /usr/bin 
or the script should be edited to /usr/sbin as a quick fix.


Anyway, this obviously easy to deal with on my end, but since this 
issue seems to exist in the stable Debian package, I thought I'd 
mention it.




--

Dan Thomson
d...@astuteinternet.com

Astute Internet Incorporated
T: 1.888.685.1661 (604.637.7939)
F: 604.738.0518
www.astuteinternet.com
100% Uptime Dedicated Hosting in Vancouver, Seattle,
Los Angeles, Toronto, New York and Miami

Follow us on Twitter: @astutehosting


___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

--- End Message ---
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] Comments regarding pg-dirtyread_1.3_amd64.changes

[Christoph Berg]

Re: Chris Lamb 2017-09-25 
<1506327842.2246848.1117103624.47cf3...@webmail.messagingengine.com>
> Hi Christoph,
> 
> > The deeper problem here is that "have debian/ inside upstream's git
> > tree" is really a pain
> 
> Indeed. My trade-offs of all the options *usually* results in going with
> *not* including debian/ in upstream's (ie. my!) git and having foo.git
> and pkg-foo.git.

Having to merge stuff all the time is exactly what I mean by "pain"
upthread. Making the package native instead makes builds from git Just
Work.

> Is this really so bad for your usecase? It is certainly more vanilla
> and straightforward... reducing the bus number for these important
> packages!

Not sure what you meant here. The package is maintained by the same
people independently from what the source format is.

Do you want me to change it before it can pass NEW?

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] Comments regarding pg-dirtyread_1.3_amd64.changes

[Christoph Berg]

Re: Chris Lamb 2017-09-25 
<1506324211.2234630.1117054560.72a88...@webmail.messagingengine.com>
> Hm. That seems wasteful.. But, outside of ftpmaster hat, are you really
> really sure you want native packages for something that isn't Debian
> specific? :)

The deeper problem here is that "have debian/ inside upstream's git
tree" is really a pain, unless the package is format 1.0 or 3.0
(native). Otherwise, (likely non-debian-savvy) upstreams will have a
hard time building packages from HEAD because each time there's a
change outside debian/, the build will fail because it doesn't match
the tarball.

Maybe I should make pg-dirtyread source format 1.0, and have it build
the diff against the latest tarball (which still exists even for 3.0
(native) because of the archive.tar.gzs from GitHub) like in the old
days.

Christoph


signature.asc
Description: PGP signature
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] PostgreSQL 10 transition

[Christoph Berg]

Re: To Ole Streicher 2017-09-23 <20170923194140.k4xeait35ofkc...@msg.df7cb.de>
> > may I ping you here? Postgresql-10 just arrived in unstable (great,
> > thanks); but I would now rather like to convert to single (and
> > bin-NMU-capable) packages instead of adding postgresql-10-q3c now, as it
> > is done f.e. for Python packages.
> > 
> > I would just do this for my own packages (pqsphere and q3c), which would
> > allow to collect experiences; but ofcourse I don't want to shoot into
> > your feet with the packaging at the postgresql site.

Btw, the transition tracker is here:

https://release.debian.org/transitions/html/postgresql-10.html

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] Bug#857770: src:postgresql-debversion: please provide a unversioned binary package

[Christoph Berg]

Re: Ole Streicher 2017-09-22 
> Hi Christoph,
> 
> may I ping you here? Postgresql-10 just arrived in unstable (great,
> thanks); but I would now rather like to convert to single (and
> bin-NMU-capable) packages instead of adding postgresql-10-q3c now, as it
> is done f.e. for Python packages.
> 
> I would just do this for my own packages (pqsphere and q3c), which would
> allow to collect experiences; but ofcourse I don't want to shoot into
> your feet with the packaging at the postgresql site.

The plan seems sensible, so please go ahead, it will be an interesting
experiment. The plethora of mini packages we have now isn't ideal.

(While uploading the first batch of PG10 packages, I rediscovered the
fact that the pgagent package is already using such a scheme:

Package: pgagent
XB-Postgresql-Version: ${Postgresql:Version}
Postgresql-Version: 9.2 9.3 9.4 9.5 9.6

The package is pretty small, though, pgagent's extension part is SQL
only, and version-agnostic, only the pgagent client binary needs to be
compiled, and doesn't vary between versions.)

My main concern is supporting upgrades cleanly. Imagine "your" package
had already been around in jessie, and the user had postgresql-9.4 +
postgresql-q3c installed where q3c provided the 9.4 extension. Now the
user upgrades to stretch, gets postgresql-9.6 installed (e.g. via
postgresql.deb), the 9.4 cluster will still work, but the upgraded
postgresql-q3c package from stretch suddenly doesn't provide the 9.4
anymore, but only 9.6, rendering q3c broken in the 9.4 cluster.

Maybe we could just claim that the user should upgrade their database
at the same time, and for many extensions this will not be a problem.
But for extensions providing datatypes (I think that includes q3c),
the .so module is needed for dumping the old data, so at least
dump-restore upgrades are affected. pg_upgrade should still work,
though. (Making pg_upgradecluster use that by default is another
story.)

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#874427: /usr/bin/pg_config in multiple packages

[Christoph Berg]

Control: tags -1 moreinfo

Re: Bryan Henderson 2017-09-06 <98655.bry...@giraffe-data.com>
> Package: postgresql-common
> Version: 165+deb8u2
> 
> Both postgresql-common and libpq-dev install the file /usr/bin/pg_config .
> That's a bug, isn't it?  dpkg --install seems to think so.

Hi Bryan,

that's not a bug, the /usr/bin/pg_config from libpq-dev is moved aside
by postgresql-common's preinst script via dpkg-divert:

diversion by postgresql-common from: /usr/bin/pg_config
diversion by postgresql-common to: /usr/bin/pg_config.libpq-dev
libpq-dev, postgresql-common: /usr/bin/pg_config

> This was not a problem for me before an attempted update a few days ago; Now I
> have broken dependencies that I cannot fix because I cannot install the
> current libpq-dev because of the file conflict.  I don't know what changed.

If the diversion didn't work for you, something is messed up. Does
"apt-get install --reinstall postgresql-common" fix things?

If there's still problems, please attach the terminal output of
apt and dpkg so we can have a look.

Christoph


signature.asc
Description: PGP signature
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] Bug#857770: src:postgresql-debversion: please provide a unversioned binary package

[Christoph Berg]

Re: Ole Streicher 2017-08-30 
> The idea here is to have just one binary package, containing the shared
> libraries for all supported versions. Extensions are usually small, so
> combining them in one package will not hurt. So, there would no
> "postgresql-9.6-q3c" package anymore, d/control.in is removed, and
> d/control is fixed (for one release). For convenience, I just attach the
> complete d/control for postgresql-q3c.
> 
> In that case, changing the supported postgresql versions will not change
> the list of binary packages, but just the dependencies, which is IMO not
> forbidden.

That is true, but it's totally different from what we have been doing
so far. We would need to update all packages, and providing the
necessary (?) transitional packages for existing users will be
difficult.

If a PG version goes out of support, the new package version wouldn't
contain the module anymore, even if users are still using that PG
version on their system. (Think Debian dist-upgrades.)

It would also prevent (easily) building packages against beta/devel PG
versions (10 and 11 at the moment). Or these packages would need to
include the "normal" PG versions from the normal packages, plus the
extra versions.

The idea is intriguing, though. Maybe these problems have cute
solutions and could be fixed.

Christoph


signature.asc
Description: PGP signature
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] Bug#857770: src:postgresql-debversion: please provide a unversioned binary package

[Christoph Berg]

Re: Ole Streicher 2017-08-30 
> For Debian (single Postgresql version) this works well; I don't know
> if "pg_buildext supported-versions" returns them line by line (what I assumed)
> or space-separated (then it needs some adjustments). One should also discuss
> which Postgresql version should be the first (which installed by default).

It's line-separated.

Re the default version, the convention is that
/usr/share/postgresql-common/supported-versions returns the default
version /last/. (Try calling
  PG_SUPPORTED_VERSIONS=pgdg /usr/share/postgresql-common/supported-versions
).

I'm not sure if "pg_buildext supported-versions" preserves that
ordering in all cases; but we can fix it to do so if it's not already
the case. Then there is the question what to do if the default version
is not in the intersection of "debian/pgversions"
`/usr/share/postgresql-common/supported-versions`, which is what
`pg_buildext supported-versions` really computes.

> Ideally the dependency generation could be integrated into pg_buildext.

Right.

> If a new Postgresql version is uploaded (or an old one is removed), a
> binNMU can be requested, resulting in a new package with the new list of
> Postgresql objects built in. As it is done for Python or others.

BinNMUs would work for updating the ${postgresql:Depends} part. What
doesn't work is changing the set of binaries built from
debian/control, because it's forbidden by Debian policy. This is why
"pg_buildext checkcontrol" raises an error if the file changes.
Possibly we could make it smarter, but in most cases, changing the
default version will mean the list of supported versions changes as
well.

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] Debian packaging of the q3c and pgsphere extensions

[Christoph Berg]

pgsphere now built successfully on apt.postgresql.org. Even including
PostgreSQL 10 and 11 :)

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] Non-versionized extension package aliases?

[Christoph Berg]

Re: Ole Streicher 2017-08-25 <4d81f803-b514-9c95-421e-173d7f21d...@debian.org>
> I first need to see how a postgresql upgrade would work at all in my
> case (still getting familar with the package). I could imagine that it
> helps to have an additional metapackage posgresql-default-pgsphere
> (depending on a postgersql-default package), and then have the dependency
> 
> Depends: postgresql-default-pgsphere | postgresql-pgsphere
> 
> in the main server package. That would install (and keep) by default the
> latest package, but also allows to work with a predefined specific
> version if the user wants this.

That should work I think.

> There is, however still some need for discussion with the gavodach upstream.
> 
> How is this solved for other applications that need postgresql + extensions?

Unsolved so far. There's a discussion in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857770

I'm still unsure if adding yet more packages next to the already very
small PG extension packages is the right step. But maybe I should just
give in and do it that way...

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] Non-versionized extension package aliases?

[Christoph Berg]

Re: Ole Streicher 2017-08-25 
> Is there already a solution for this? Shall I use
> 
> Provides: postgresql-pgsphere
> 
> for all versionized extension packages?

Makes sense I think.

Note that it doesn't make PostgreSQL upgrades work, e.g. if you switch
from jessie to stretch, it won't automatically pull in
postgresql-9.6-pgsphere if you had postgresql-9.4-pgsphere installed
before, as both provide postgresql-pgsphere. We'd need real meta
packages for that, but that would mean even more .debs, which I'd be
reluctant to add.

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] Debian packaging of the q3c and pgsphere extensions

[Christoph Berg]

Re: To Ole Streicher 2017-08-07 <20170807193234.2tubkvnei75yq...@msg.df7cb.de>
> Re: To Ole Streicher 2017-08-07 <20170807192924.lzdjji4poyqmc...@msg.df7cb.de>
> > The tests seem to work for the apt.postgresql.org jenkins as well.
> > (Still building, the tests are pretty slow and there's 5 "9.x"
> > versions to cover.)
> 
> Sorry I spoke too soon - sid/amd64 works, but ppc64el has problems:
> 
> 00:06:24.415 cat sql/ellipse.sql | psql q3c_test > results/ellipse.out
> 00:06:31.011 diff results/ellipse.out expected/ellipse.expected
> 00:06:31.012 2838c2838
> 00:06:31.012 <804
> 00:06:31.012 ---
> 00:06:31.012 >803
> 00:06:31.013 Makefile:37: recipe for target 'test' failed

Reported upstream now as https://github.com/segasai/q3c/issues/11.

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] Debian packaging of the q3c and pgsphere extensions

[Christoph Berg]

Re: Ole Streicher 2017-08-18 <73ec8047-2a1d-f125-f8a1-2bb86b7a3...@debian.org>
> (mailing list removed for the moment due to the large attachment)

(Added back now.)

> Thank you for the report! I am just adding the full log file for Markus
> (I can't do much myself here and rely on upstream). Markus, could you
> have a look? Or shall I open an issue on the upstream github myself?
> 
> Christoph, would you mind to open a Debian bug for this? That way, it is
> not forgotten :-)

I just filed a GitHub issue: https://github.com/akorotkov/pgsphere/issues/5

> When I looked into the log, the bug appears with postgresql 9.2. Does
> the same error happen, or is it expected to happen with the current
> version 9.6 as well (which is the only one in Debian testing for the
> moment)?

I'd be very surprised if the PG version played any substantial role
here. The differences all seem to be related to endianess or FP
rounding. Also, I know that Alexander is doing PG development on
PowerPC, so he'll be testing any patches on PG master HEAD and will
spot any problems anyway.

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#872915: Bug#759725: postgresql-common: non-synchronous service postgresql stop

[Christoph Berg]

(Moving to #872915 because #759725 was about stopping PostgreSQL, not
starting it)

Re: Ludovic Gasc 2017-08-22 

[Pkg-postgresql-public] Bug#759725: postgresql-common: non-synchronous service postgresql stop

[Christoph Berg]

Re: Ludovic Gasc 2017-08-22 

Re: [Pkg-postgresql-public] [pgsql-pkg-debian] Debian packaging of the q3c and pgsphere extensions

[Christoph Berg]

Re: Ole Streicher 2017-08-17 
> Markus replied to me and reminded me that I shouldn't use the tarball
> but the current git repository for the moment.
> 
> What I did, resulting in successful tests. Since Lintian didn't complain
> (and for me personally everything looks good), I uploaded the package;
> it should appear on NEW soon (which has a long queue in the moment,
> unfortunately).
> 
> Thank you very much for the help, and I am open for more comments :-)

Hi,

nice :)

I've just triggered a build on the apt.postgresql.org jenkins.
Unfortunately, pgsphere is failing the regression tests on ppc64el due
to floating point differences (e.g. 0 vs -2.38158728306e-17). This is
likely just different rounding, but this looks like a real bug:

00:01:42.739   SELECT '( 0h 2m 30s ,-90d 0m 0s)'::spoint;
00:01:42.739 ! spoint
00:01:42.739 ! --
00:01:42.739 !  (  0d 37m 30s , -90d  0m 0s)

00:01:42.743   SELECT '( 0h 2m 30s ,-90d 0m 0s)'::spoint;
00:01:42.743 ! spoint
00:01:42.743 ! --
00:01:42.743 !  (  0d 37m 30s , - 0d  0m -8262s)

The full build logs are at
https://pgdgbuild.dus.dg-i.net/job/pgsphere-binaries/1/
https://pgdgbuild.dus.dg-i.net/job/pgsphere-binaries/1/architecture=ppc64el,distribution=sid/console

(Needs a certificate from sso.debian.org for access)

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#871986: Bug#871986: postgresql-9.6: PostgreSQL fails to start after upgrade

[Christoph Berg]

Control: tags -1 moreinfo

Re: Jacob Sparre Andersen 2017-08-13 
<150261237312.2459.10119247764903837989.report...@franka.jacob-sparre.dk>
> Last night I upgraded "postgresql-9.6" to the most recent version
> (went from 9.6.3-3 to 9.6.4-0+deb9u1).
> 
> As a part of the upgrade PostgreSQL was shut down, and it has not come
> up since then.

Hi Jacob,

can we see the output of "systemctl status postgresql@9.6-main"?

Is /etc/postgresql/9.6/main/start.conf set to "auto"?
Do you have /usr/sbin/policy-rc.d installed?

> I've tried "sudo service postgresql restart" without any visible effect.

postgresql.service is just a stub which forwards all actions to the
individual services like postgresql@9.6-main.service. Unfortunately
systemctl doesn't really relay any errors back if there's any.

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] [pgsql-pkg-debian] Debian packaging of the q3c and pgsphere extensions

[Christoph Berg]

Re: To Ole Streicher 2017-08-07 <20170807193234.2tubkvnei75yq...@msg.df7cb.de>
> Sorry I spoke too soon - sid/amd64 works, but ppc64el has problems:
> 
> 00:06:24.415 cat sql/ellipse.sql | psql q3c_test > results/ellipse.out
> 00:06:31.011 diff results/ellipse.out expected/ellipse.expected
> 00:06:31.012 2838c2838
> 00:06:31.012 <804
> 00:06:31.012 ---
> 00:06:31.012 >803

The problem is in pgq3c_ellipse_query_it/q3c_ellipse_query. I haven't
debugged anything, but my bet would be on floating point differences
on ppc64el, maybe because of floating point contraction (fmadd, fused
multiply add). I've had such a case before, but there only
Ubuntu/ppc64el was affected.

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] [pgsql-pkg-debian] Debian packaging of the q3c and pgsphere extensions

[Christoph Berg]

Re: To Ole Streicher 2017-08-07 <20170807192924.lzdjji4poyqmc...@msg.df7cb.de>
> The tests seem to work for the apt.postgresql.org jenkins as well.
> (Still building, the tests are pretty slow and there's 5 "9.x"
> versions to cover.)

Sorry I spoke too soon - sid/amd64 works, but ppc64el has problems:

00:06:24.415 cat sql/ellipse.sql | psql q3c_test > results/ellipse.out
00:06:31.011 diff results/ellipse.out expected/ellipse.expected
00:06:31.012 2838c2838
00:06:31.012 <804
00:06:31.012 ---
00:06:31.012 >803
00:06:31.013 Makefile:37: recipe for target 'test' failed

The full build log is at
https://pgdgbuild.dus.dg-i.net/job/postgresql-q3c-binaries/1/
https://pgdgbuild.dus.dg-i.net/job/postgresql-q3c-binaries/1/architecture=ppc64el,distribution=stretch/console

(Needs a SSO certificate from sso.debian.org)

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] [pgsql-pkg-debian] Debian packaging of the q3c and pgsphere extensions

[Christoph Berg]

Re: Ole Streicher 2017-08-07 
> > ... and a minimal debian/tests/control file. (See pg_buildext(1))
> 
> Ah, so there are no built time checks possible "just" CI test, right?

Unfortunately, right. The problem is (among others) that "CREATE
EXTENSION" wants to read the $extension.control file from
/usr/share/postgresql/$version/extension, and that part is not
configurable. (There's more path problems, but the others should be
possible to work around without patching the PostgreSQL server.)

> The tests worked for me, so I didn't change this.

Not sure what was wrong on my notebook here, but that doesn't really
matter anyway :)

The tests seem to work for the apt.postgresql.org jenkins as well.
(Still building, the tests are pretty slow and there's 5 "9.x"
versions to cover.)

> Thanks for you help! Everything seems to work now, so I uploaded q3c:
> 
> https://ftp-master.debian.org/new/postgresql-q3c_1.5.0-1.html

Nice :)

> For pgsphere, I had less success; the tests fail currently. For me
> (being still a strawmen), this looks like an upstream problem, so I am
> hoping for a response from there. If you like, you can however have a
> look as well; just to double-check that it is not a packaging problem:

I'm just browsing the source - I think core of the problem is that
pgsphere was last updated in 2010 when PostgreSQL 9.0 was current -
that was the last version without "CREATE EXTENSION" support, so it's
still using the old style of directly loading the function definitions
into the server, see sql/init.sql: "\i pg_sphere.sql". 9.0 is EOL, so
you don't need to support that style anymore.

Because of the out-of-tree build, pg_sphere.sql is not in $PWD, so
psql (or pg_regress) doesn't find it when running the tests:
regression.diffs says "pg_sphere.sql: No such file or directory".
(The PostgreSQL project still likes "context" diffs for this...)

The ideal way forward would be if you convert the module to a proper
extension. Basically you just need to write a trivial pg_sphere.control
file (see q3c for an example), and install pg_sphere.sql as
pg_sphere--1.sql. (The number there is sort of the SONAME of the
extension and might or might not correlate with the upstream version
number.)

sql/init.sql could then simply say "CREATE EXTENSION pg_sphere;".
(And expected/init.sql needs to match.)

If you expect a non-trivial number of users to have installed
pg_sphere using the "\i" method, you could also provide a
pg_sphere--unpackaged--1.sql file to allow "importing" the module
objects into an extension using "ALTER EXTENSION ADD" commands. The PG
docs cover that case as well:

https://www.postgresql.org/docs/9.6/static/extend-extensions.html

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] [pgsql-pkg-debian] Debian packaging of the q3c and pgsphere extensions

[Christoph Berg]

Re: Ole Streicher 2017-08-04 <1c160beb-9ece-000c-628f-77a6f19db...@debian.org>
> I have polished both packages, with the repository still in the
> debian-science section (but I will move them to pkg-postgresql as soon
> as I become a member). They look fine to me now (except tests; see
> below), but could you have a look there?

Alioth says you are a pkg-postgresql member.

> > I'd also like to include the packages on apt.postgresql.org.
> 
> Sure, however this is out of my own scope.

I'll take care of that part - the build system there is just
rebuilding packages either from git or from "apt-get source", so
getting the packages ready in Debian first is a natural step to do
before.

> > Fwiw, I'd strongly recommend to add a debian/tests/ testsuite (see
> > also pg_buildext(1)), even if it's just a "create extension q3c;", so
> > we have some test coverage.
> 
> I'd love to. Especially q3c has this already enabled. However I don't
> know how to enable a test postgresql database server. When I just add
> postgresql-client to d/control[.in], I get
> 
> createdb q3c_test
> createdb: could not connect to database template1: could not connect to
> server: No such file or directory
>   Is the server running locally and accepting
>   connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
> Makefile:37: recipe for target 'test' failed
> 
> during the build. Do you have any hints here?

pg_virtualenv. "pg_buildext installcheck" will use it to create
throw-away database clusters for testing.

Unless you need to do special setup steps, all you'd need is:

debian/tests/installcheck:
#!/bin/sh
pg_buildext installcheck

... and a minimal debian/tests/control file. (See pg_buildext(1))


So much for the generic hints - I've taken a look at the actual
q3c package in the meantime :)

Firstly, upstream seems to work hard on avoiding pg_regress - the
whole "diff" logic in the Makefile could likely be avoided by just
putting

REGRESS = ang2ipix area cone_join_rev cone ellipse join poly version

into the Makefile. "make installcheck" would then take care of all the
work. (But it's probably not our job as packagers to fix that...)

A real problem is that the Makefile doesn't install the
scripts/q3c--1.5.0.sql file because of its use of $(wildcard) - you'll
need to replace that with a static list of files to install, or move
from "pg_buildext build/install" to "pg_buildext loop".

The testsuite seems to almost work except for one diff here:

diff results/version.out expected/version.expected
3c3
<  f
---
>  t

The actual debian/tests/installcheck file could be something like:

#!/bin/sh
for v in $(pg_buildext supported-versions); do
  LC_ALL=C pg_virtualenv -v $v make test
done

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] [pgsql-pkg-debian] Debian packaging of the q3c and pgsphere extensions

[Christoph Berg]

Re: Ole Streicher 2017-07-31 
> I am posting to both lists since I am unsure where the best place is. I
> am however not subscribed to any of them, so please keep in Cc for the
> moment:

Hi Ole,

both lists are fine.

> As a dependency of the Virtual Observatory "DACHS" package [1], which I
> am planning to package, I need to have the "q3c" [2] and "pgsphere" [3]
> packages in Debian. All packages already exist in a separate repository
> [4]; the initial packaging was done by Florian Rothmaier.

Florian was talking to me about these some years back, iirc we were
close to getting the packages polished up, but then communication got
stuck at some point. Thanks for taking this up again!

I'd also like to include the packages on apt.postgresql.org.

> However, I am very new to Postgresql extension packaging, and therefore
> I would ask to get some useful hints here. Especially: Is there a Debian
> policy for postgresql extensions that documents the preferred way for
> packaging?

pg_buildext(1) and dh_make_pgxs(1) (both from postgresql-server-dev-all)
should provide a working skeleton at least for the case of extension-only
packages.

> A preferred git repository? Or is the Debian Science git
> repository OK?

Any git repo works.

> Are extensions dependent on the postgresql version, and
> if yes, how should I create the package to enable smooth transitions?

The server major version is encoded in the .so files built and the
path names, so they are dependent, yes.

> What are the preferred names for the packages?

postgresql-9.6-q3c etc.

> I would be glad to get some initial startup here (maybe a simple
> template or so)?

See pg_buildext(1) and dh_make_pgxs(1).

The existing

https://anonscm.debian.org/cgit/debian-science/packages/q3c.git/
https://anonscm.debian.org/cgit/debian-science/packages/pgsphere.git/

repositories seem mostly fine even by today's packaging standards
(maybe some of the extra clutter in debian/rules could be removed), so
you should probably go from there.

Fwiw, I'd strongly recommend to add a debian/tests/ testsuite (see
also pg_buildext(1)), even if it's just a "create extension q3c;", so
we have some test coverage.

Thanks,
Christoph


signature.asc
Description: PGP signature
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] About the security issues affecting postgresql-pljava in Wheezy

[Christoph Berg]

Re: Raphael Hertzog 2017-06-20 <20170620162214.kxf3y2ksrxkai...@home.ouaza.com>
> That said the wheezy users would most certainly benefit from a fixed
> package and it looks like the issues have all been fixed in 1.5.0 and
> 1.5.1 so it should be possible to apply upstream fixes.

Last time I checked, packaging 1.5 is tantamount to packaging half of
the java world due to missing dependencies.

I haven't checked the necessary patches, but unless someone wants to
put in the effort of properly bringing pljava back to unstable, we
should probably just declare wheezy dead and not fix pljava 1.4 in
there.

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#865020: Bug#865020: Bug#865020: postgresql-9.6: FTBFS with Perl 5.26: hstore_plperlu differences

[Christoph Berg]

Re: Niko Tyni 2017-06-20 <20170620113058.ga5...@hagar.it.helsinki.fi>
> > So it's perhaps not worth patching around in it before then.
> 
> Your call, though I'd certainly appreciate if you included it
> if there's to be another 9.6.3 upload in between.

I don't think there would be an upload, but we'd of course include the
fix if there's one.

> We're tracking sid with the unofficial binNMU repo at perl.debian.net,
> and this shows up on the radar of packages that can't currently be
> rebuilt. I don't think it's blocking other packages atm though.

There should be no relevant reverse dependencies that wouldn't just
work with the existing 9.6.3 packages as well.

> We don't have a schedule for 5.26 in sid yet, but things are looking
> quite good this time [at least compared to some previous years :) ]

I'm especially looking forward to libperl5.26 being co-installable
with libperl5.24, this will save postgresql-plperl some upgrade
headaches :)

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] pg_ctlcluster stop does not read pg_ctl.conf

[Christoph Berg]

Re: Badics, Alex 2017-06-12 

Re: [Pkg-postgresql-public] pg_ctlcluster stop does not read pg_ctl.conf

[Christoph Berg]

Re: Badics, Alex 2017-06-12 

[Pkg-postgresql-public] Bug#863928: postgresql-9.6: FTBFS: test failures

[Christoph Berg]

Control: tags -1 moreinfo

Re: Lucas Nussbaum 2017-06-02 <20170602020100.unhbpb6fzyyfw...@xanadu.blop.info>
> > pg_regress: initdb failed
> > Examine /<>/build/src/test/regress/log/initdb.log for the 
> > reason.
> > Command was: "initdb" -D 
> > "/<>/build/src/test/regress/./tmp_check/data" --noclean 
> > --nosync > "/<>/build/src/test/regress/log/initdb.log" 2>&1

Hi Lucas,

I can't reproduce the problem on stretch/i386 here. Unfortunately the
logic in debian/rules for printing initdb.log on failure doesn't
really work - I've pushed a change to git that would fix it, but I'm
unsure if that alone warrants a new upload.

https://anonscm.debian.org/cgit/pkg-postgresql/postgresql.git/commit/?h=9.6=0bbd694b81d0ddb0fe218798288067fe24113af7

> LANG=en_US.UTF-8
> LC_ALL=POSIX

Does the en_US.UTF-8 locale exist in the build environment? (LC_ALL
should overwrite it, but that's my best guess at the moment.)

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] issue setting up postgresql-client-9.6 on stretch

[Christoph Berg]

Re: Ernesto Ongaro 2017-05-24 

> Using docker images, slimmed down version of debian that doesn't have man
> installed and looks for missing directory. Any idea how to work around?
> Package doesn't depend on man being installed.

Hmm, do you have any idea how the "official" "postgres" packages on
docker hub solve that issue? I thought they were based on our
packages.

> update-alternatives: error: error creating symbolic link
> '/usr/share/man/man1/psql.1.gz.dpkg-tmp': No such file or directory

Possibly we just need to ship /usr/share/man/man1 in the package.

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#863256: Enable dtrace

[Christoph Berg]

Package: postgresql-10
Version: 10~beta1-1
Severity: wishlist

We should think about --enable-dtrace.

Asked about by sebl on #postgresql-apt.

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] weird issue with odbc-postgresql on armbian

[Christoph Berg]

Re: Andrés Ramírez 2017-05-11 <87k25ot05x@gmail.com>
> --8<---cut here---start->8---
> Program received signal SIGILL, Illegal instruction.
> 
> Program received signal SIGSEGV, Segmentation fault.

> I have been reading and seems to be an issue with the stack on my arm
> device (orange pi plus 2e). The device have armbian (debian jessie)
> installed.

Hi,

SIGILL means the compiler produced something that the device couldn't
execute. This is almost certainly a problem with the armbian
toolchain.

Christoph


signature.asc
Description: PGP signature
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] Debian "postgresql-common" config check issue with pg10

[Christoph Berg]

Re: Fabien COELHO 2017-05-08 
> Thus I naïvely added:
> 
>   password_encryption = scram-sha-256

Hmm. Naïvely I would have assumed this would be missing quotes :)

> The result is:
> 
>   Error: Invalid line 88 in /etc/postgresql/10/main/postgresql.conf:
> »password_encryption = scram-sha-256«
> 
> However, it works if I put 'scram-sha-256' (with simple quotes).
> 
> The underlying issue is that the '-' character breaks the config checker,
> ISTM that the simple value regex in function "read_conf_file" in module
> "PgCommon.pm" should be extended to allow more chars in unquoted strings, to
> be consistent with lexer definitions in "src/backend/utils/misc/guc-file.l".

I've relaxed the regexps there. It's still not exactly what the PG
parser accepts, but I think it's a superset now, so we should be safe.

https://anonscm.debian.org/cgit/pkg-postgresql/postgresql-common.git/commit/?id=93a2ec91ea83e427fc2e68789e572864e158a32e

> In passing, I would like to point out that the French quotation chevrons
> (guillemets) used on the wrong sides and without spacing is probably eye
> watering pain to any French reader, maybe like using ß in place of B in a
> text. Also utf8 chars might not work properly under some terminal encodings.
> Maybe using simple ascii ">>" and "<<" for the messages would also be more
> portable?

I think »« are used the other way round in German vs. French, that's
probably why it was like that ;). Anyway, we are not quoting output in
most of the error() calls, so I've simply dropped the quotes.

Thanks for spotting and reporting!

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] Wheezy update of postgresql-common?

[Christoph Berg]

Re: Ola Lundqvist 2016-12-20 <20161220215504.ga24...@inguza.net>
> Hello dear maintainer(s),
> 
> the Debian LTS team would like to fix the security issues which are
> currently open in the Wheezy version of postgresql-common:
> https://security-tracker.debian.org/tracker/CVE-2016-1255
> 
> Would you like to take care of this yourself?

Yes.

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#856025: [pgadmin3] Please pack pg admin 4

[Christoph Berg]

Re: Michael Meier 2017-02-24 
> Package: pgadmin3
> Version: 1.22.2-1
> Severity: wishlist
> 
> pg admin 4 is out since a while and pg admin 3 is not supported anymore.
> It would be great if you could pack the new version.

Hi,

see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834129

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#855606: sqrt() regression on powerpc/jessie

[Christoph Berg]

Package: libc6
Version: 2.19-18+deb8u7
Severity: normal
Tags: jessie

The following C program produces different output on Jessie and Sid. I
believe the Sid output is the correct one, and in fact this is the
output that has been observed for the "point" (and "polygon")
regression tests for PostgreSQL on all platforms for the last 20 years
since the test got added.


$ cat sqrt.c
#include 
#include 
#include 

double
pg_hypot(double x, double y)
{
double  yx;

/* Some PG-specific code deleted here */

/* Else, drop any minus signs */
x = fabs(x);
y = fabs(y);

/* Swap x and y if needed to make x the larger one */
if (x < y)
{
double  temp = x;

x = y;
y = temp;
}

/*
 * If y is zero, the hypotenuse is x.  This test saves a few cycles in
 * such cases, but more importantly it also protects against
 * divide-by-zero errors, since now x >= y.
 */
if (y == 0.0)
return x;

/* Determine the hypotenuse */
yx = y / x;
return x * sqrt(1.0 + (yx * yx));
}


int main ()
{
//fesetround(FE_TONEAREST);
printf("fegetround is %d\n", fegetround());
double r = pg_hypot(10.0, 10.0);
printf("14 %.14g\n", r);
printf("15 %.15g\n", r);
printf("16 %.16g\n", r);
printf("17 %.17g\n", r);
return 0;
}


Jessie output:
fegetround is 0
14 14.142135623731
15 14.1421356237309
16 14.14213562373095
17 14.142135623730949

Sid output:
fegetround is 0
14 14.142135623731
15 14.142135623731
16 14.14213562373095
17 14.142135623730951


The Sid output is also observed when running the binary compiled on
Jessie on Sid, so it's a library issue, not a compiler/binary one.


The problem might be due to the fix for #843904.


FTBFS in postgresql-9.4 in jessie-pu:
https://buildd.debian.org/status/fetch.php?pkg=postgresql-9.4=powerpc=9.4.11-0%2Bdeb8u1=1487473754=0
FTBFS in postgresql-9.6 in jessie-backports:
https://buildd.debian.org/status/fetch.php?pkg=postgresql-9.6=powerpc=9.6.1-2~bpo8%2B1=1485184696=0

Thread on pgsql-hackers:
https://www.postgresql.org/message-id/20170220155819.m2s43pf2pvkes4pc%40msg.credativ.de

Christoph


signature.asc
Description: PGP signature
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] #834129

[Christoph Berg]

Re: Kamil Pazik 2017-02-12 

> Hi Christoph,
> 
> I'm writing to you regarding bug #834129
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834129
> 
> I'm willing to create package of pgadmin 4.
> 
>- I already met debian developers in my city, next time they gonna sign
>me my key
>- I compiled pgadmin4
>- And I'm in progress of getting know how to make good packages
> 
> I will appreciate if you give me some hints how to cooperate. Because I'm
> fresh with Debian packaging and community.
> 
> Best regards,
> Kamil Pazik

Hi Kamil,

thanks for your interest!

Most of https://wiki.debian.org/DebianMentorsFaq applies to the
PostgreSQL packages as well, so start there, especially all the other
FAQs and HOWTOs linked from there.

I'm mostly available on IRC, if you stop my on #postgresql-apt on
irc.freenode.net (not oftc in this case), we can help you sort out the
package. Or ask on the mailing list (Cc'ed). (Be aware though that
this is a non-trivial task, this is a web app that can also run as
desktop app, the packaging layout will need some original research to
be done.)

Christoph
-- 
Senior Berater, Tel.: +49 2166 9901 187
credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209
Trompeterallee 108, 41189 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer
pgp fingerprint: 5C48 FE61 57F4 9179 5970  87C6 4C5A 6BAB 12D2 A7AE

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#854997: Bug#854997: postgresql-9.6: autopkgtest for pg-repack failing

[Christoph Berg]

Re: Jeremy Bicha 2017-02-13 

> Source: postgresql-9.6
> Version: 9.6.2-1
> Severity: important
> X-Debbugs-CC: nthyk...@debian.org
> 
> On both Ubuntu and Debian, the recent upload of postgresql-9.6 9.6.2-1
> appears to have caused pg-repack's autopkgtests to begin failing.
> 
> https://ci.debian.net/packages/p/pg-repack/unstable/amd64/
> 
> I see on https://tracker.debian.org/pkg/postgresql-9.6 that this
> update has been unblocked for stretch, but maybe this should be fixed
> or investigated first.

Thanks for reporting. It's very much likely a problem in pg-repack,
though... I'll investigate.

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] typo in pg_upgradecluster

[Christoph Berg]

Re: victory 2017-01-16 <20170117014450.17d0cd7dd00e97e3fcad9...@gmail.com>
> 
> pg_upgradecluster:545:
>   error 'Could not ANALZYE database';
> ^^

Hi,

thanks for spotting - it has already fixed in git back in October and
was released in postgresql-common 171.

Christoph


signature.asc
Description: PGP signature
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] postgresql-9.6 in jessie-backports?

[Christoph Berg]

Re: Jan Wagner 2017-01-05 <e523dde9-938e-e0d2-d38d-350cf494e...@cyconet.org>
> Hi Christoph,
> 
> Am 04.01.17 um 15:32 schrieb Christoph Berg:
> > As much as I like backports, I'd rather not have to do yet another set
> > of uploads on each round of PostgreSQL minor releases.
> 
> might it be an option after freeze/release of stretch as there shouldn't
> be so much updates afterwards?

We still upload every PG release to all supported distributions, so it
doesn't make a difference if stretch is frozen or not.

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] postgresql-9.6 in jessie-backports?

[Christoph Berg]

Re: Evgeni Golov 2017-01-04 
<20170104131426.hstzf6sv5e3jg...@t440s.egolov.redhat.com>
> Hey,
> 
> On Wed, Jan 04, 2017 at 01:58:14PM +0100, Jan Wagner wrote:
> > as postgresql-9.6 seems to be the postgresql version released with
> > stretch, is it (and postgresql-common) planed to be backported to
> > jessie-backports?
> 
> PostgreSQL has a very colorful bikeshed at [1], which is maintained by
> the official maintainers. Any reason not to use that?

The last round of jessie-to-wheezy backports was done because a
customer was specifically asking for sparc packages which
apt.postgresql.org doesn't provide.

As much as I like backports, I'd rather not have to do yet another set
of uploads on each round of PostgreSQL minor releases.

Christoph


signature.asc
Description: PGP signature
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#848869: Error: could not create default cluster. Please create it manually with

[Christoph Berg]

Control: tags -1 moreinfo

Re: Darshaka Pathirana 2016-12-20 
<20161220110151.19348.48480.reportbug@invincible>
>   Error: The locale requested by the environment is invalid.

> Locale looks like this:
> 
>   % locale
>   LANG=en_US.UTF-8
>   LANGUAGE=en_US:en

Hi,

on package installation (only), the locale used for pg_createcluster
(= initdb) is not determined by your environment (which "locale" looks
at), but by the system configuration in /etc/environment and
/etc/default/locale.

Could you check what you have configured in these files?

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#846019: pgadmin3: SIGABRT after fatal error complaint regarding libwxgtx ABI mismatch

[Christoph Berg]

Re: Björn Harrtell 2016-12-08 

Re: [Pkg-postgresql-public] how to get a local/minimal per-user postgresql server on debian?

[Christoph Berg]

Re: Daniel Kahn Gillmor 2016-11-11 <87wpgafb5a@alice.fifthhorseman.net>
> Thanks for the pointers, i think this gives me enough to chew on for the
> moment.  These suggestions don't really help with minimizing the
> dependency chain, of course, but that sort of "postgresql-light" rebuild
> might not be worth the effort.

I don't think it would be. The "extra dependency" footprint of
postgresql-N.N on a typical system is often zero (e.g. libldap is
often already there anyway), and even postgresql-contrib-N.N will only
pull very few extra libraries. I'm even pondering fully merging the
contrib package into the main server package, but haven't decided yet.

Thanks for your input!

Christoph


signature.asc
Description: PGP signature
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] how to get a local/minimal per-user postgresql server on debian?

[Christoph Berg]

Re: Daniel Kahn Gillmor 2016-11-10 <8737iz5klm@alice.fifthhorseman.net>
> Hi Debian PostgreSQL folks--
> 
> Thre are some circumstances where i'd like to have the postgresql
> binaries available without necessarily needing the system services
> installed and started.  For example, i have a set of intermittent
> short-lived processes that need to share long-lived state.  The state is
> best described as a relational database, but i want all that state to be
> under control of the unix user account that executes the processes, and
> not under control of some other system user like postgres.

Hi,

PG is not going to be an embedded database, so there will never be
something like a libpostgresql that you could link to and have the DB
"inside" your program. It will always be a (set of) separate
processes. Which means you'll need infrastructure to "boot" it.

postgresql-common supports "user clusters", i.e. you can point
PG_CLUSTER_CONF_ROOT to some place where the config should be, and
also ask for the data directory to be elsewhere. I haven't tested how
compatible this is with "user" systemd instances, but it's probably
not too hard to get it running. (See pg_wrapper(1).)

Also, I'm not sure why you would want to avoid the dependency on
postgresql-common, if you don't want the service files or pg_*cluster,
just don't use it? (If you want to avoid the "main" cluster to be
created on postgresql-N.N install, add "create_main_cluster = false"
to /etc/postgresql-common/createcluster.conf before installing the package.)

I'm not sure this answers all of your questions, but before I'm
answering everything from the wrong perspective, does this address
your use case?

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#843893: Optionally refuse non-root pg_ctlcluster operation to enforce proper systemd usage

[Christoph Berg]

Package: postgresql-common
Version: 177
Severity: wishlist

10 14:37  Myon: thoughts on having a config switch to turn "Warning: 
the cluster will not be running as a systemd service. Consider using 
systemctl:\n" into a hard error instead?
10 14:38  I've wondered if it can just invoke systemctl if it's being 
run as root.
10 14:39  Berge: it does, it only warns if postgres invokes pg_ctlcluster
10 14:39  ah, nice
10 14:39  magnush: I think that would freak out everyone trying to start 
postgres as "postgres"
10 14:39  it does refuse to restart a systemd cluster as postgres
10 14:40  magnush: imho the only viable fix would be to allow postgres to 
properly start/stop services, and that doesn't seem feasible atm
10 14:40  What's a systemd cluster?
10 14:40  Myon: i'm not saying it should do so by default. I'm saing 
I'd like a way to in an installation make sure that people don't accidentally 
stat it as postgres
10 14:40  because the nit's not a systemd unit
10 14:40  which means the system can loose sync between them and not 
figure out when it's running at all.
10 14:40  Berge: I mean a PostgreSQL instance running properly from 
systemd
10 14:40  Myon: ah, right
10 14:40  magnush: nod
10 14:40  So I want to,m for this specific installation, *force* 
people to start/stop using systemd. SOP still tells them to always do that, but 
I want to enfforce it.
10 14:42  I generally agree, but that leads to even more warts on an 
already a-tad-too-complicated system
10 14:42  Myon: a simple setting somewhere in /etc/postgresql-common 
wouldn't be all that difficult would it? And I could easily provision it out 
with the customer puppet setup :P
10 14:44  I think the proper place would be (the per-cluster) 
pg_ctl.conf, and on top of that, a gobal pg_ctl.conf to provide the defaults

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] OpenSSL 1.1.0 and reverse build-dependencies of libpq-dev

[Christoph Berg]

Re: Carsten Leonhardt 2016-11-02 <871syuywdw@arioch.leonhardt.eu>
> Dear Postgres Packagers,
> 
> The new libssl1.0-dev and libssl-dev packages conflict with each other,
> so cannot be mixed during a package build.
> 
> Because my pacakge bacula links with both libssl and libpq, it looks
> like I need to coordinate with you.
> 
> Do you plan to release a new version of libpq-dev that depends on
> libssl1.0-dev or will you stay with libssl-dev (and thus switch to
> openssl 1.1)?

You should switch to 1.1 if that's an option :), but as we are just
discussing on #debian-devel, the libssl-dev dependency of libpq-dev
will simply go away completely. I'll be uploading later today.

Thanks for making us aware,
Christoph


signature.asc
Description: PGP signature
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#842752: Bug#842752: postgresql-9.6: FTBFS: test failures on i386/armel/armhf

[Christoph Berg]

Re: Emilio Pozuelo Monfort 2016-11-01 
<147795902108.24771.17991504514045017206.reportbug@tatooine>
> Source: postgresql-9.6
> Version: 9.6.1-1
> Severity: serious
> 
> Your package failed to build on i386, armel and armhf with test errors.
> 
> See the logs at https://buildd.debian.org/status/package.php?p=postgresql-9.6

Fwiw, the real bug is in Linux, which manifests because the buildds
are using a jessie kernel:
#797530: 32bit pie memory layout leaves only ~100MB between heap and stack.

We'll work around it in PostgreSQL by explicitly disabling PIE on
32bit. (The previous workaround was to not enable it there, but the
default has changed.)

I'd prefer a proper fix in the kernel, though.

Christoph


signature.asc
Description: PGP signature
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] Feature proposal : knob to prevent clusters from being stopped by dpkg

[Christoph Berg]

Re: Pierre Ducroquet 2016-10-05 <2384876.jxRJq2Nt6j@laptop-pierred>
> Hi
> 
> In order to ease maintenance and reduce downtimes, we would like in our 
> environment to control ourselves when the postgresql clusters are shut down 
> (in order to synchronize with pausing the bouncer for instance)
> This is currently not possible with the debian postgresql packages, where a 
> minor upgrade will shut down, upgrade and restart the cluster.
> I propose the attached simple patch, adding a check on a /etc/postgresql-
> common/disable-unattended-restart file. If that file is present, clusters are 
> not stopped.
> Would this behaviour change be acceptable ? If so, what is the proper way to 
> submit a patch to the package ?

Hi,

the proper way to do that is supplying a /usr/sbin/policy-rc.d file, e.g.


#!/bin/sh

while true; do
  case "$1" in
-*) shift ;;
makedev)exit 0;;
*)
  exit 101
  ;;
  esac
done


https://people.debian.org/~hmh/invokerc.d-policyrc.d-specification.txt


Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

[Pkg-postgresql-public] Bug#839630: postgresql-9.5 should not be in testing

[Christoph Berg]

Package: postgresql-9.5
Version: 9.5.4-3
Severity: serious

postgresql-9.5 will be removed soon and should not be in testing until
then.

Christoph


signature.asc
Description: PGP signature
___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] solving problem

[Christoph Berg]

Re: mohamed zangana 2016-10-02 

> Hello
> I make apgrade for my kalilinux 2016.2 and i have problem in postgresql
> server
> I delete this  file ( README.Debian.gz ) please how i can download it

There's several packages that ship a file named like that. The
directory name in /usr/share/doc// will tell you
the package name. Then do:

apt-get install --reinstall this_package_name

Christoph

___
Pkg-postgresql-public mailing list
Pkg-postgresql-public@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Re: [Pkg-postgresql-public] libdbi-drivers FTBFS due to different PostgreSQL versions

[Christoph Berg]

Re: László Böszörményi (GCS) 2016-09-20