debian/0000755000000000000000000000000013335072071007167 5ustar debian/postgresql-doc-9.3.install0000644000000000000000000000011113334546526014037 0ustar usr/share/doc/postgresql-doc-9.3/html usr/share/postgresql/9.3/man/man3/ debian/libpgtypes3.install0000644000000000000000000000003113334546551013026 0ustar usr/lib/libpgtypes.so.3* debian/tests/0000755000000000000000000000000013334546526010343 5ustar debian/tests/control0000644000000000000000000000021113334546526011740 0ustar Tests: run-testsuite Depends: @, build-essential, hunspell-en-us, locales, netcat-openbsd, net-tools, logrotate Restrictions: needs-root debian/tests/run-testsuite0000755000000000000000000000007613334546526013127 0ustar #!/bin/sh set -e cd /usr/share/postgresql-common ./testsuite debian/libpgtypes3.symbols0000644000000000000000000000263013334547710013055 0ustar libpgtypes.so.3 libpgtypes3 #MINVER# PGTYPESchar_free@Base 9.3.24 PGTYPESdate_dayofweek@Base 0 PGTYPESdate_defmt_asc@Base 0 PGTYPESdate_fmt_asc@Base 0 PGTYPESdate_free@Base 0 PGTYPESdate_from_asc@Base 0 PGTYPESdate_from_timestamp@Base 0 PGTYPESdate_julmdy@Base 0 PGTYPESdate_mdyjul@Base 0 PGTYPESdate_new@Base 0 PGTYPESdate_to_asc@Base 0 PGTYPESdate_today@Base 0 PGTYPESdecimal_free@Base 0 PGTYPESdecimal_new@Base 0 PGTYPESinterval_copy@Base 0 PGTYPESinterval_free@Base 0 PGTYPESinterval_from_asc@Base 0 PGTYPESinterval_new@Base 0 PGTYPESinterval_to_asc@Base 0 PGTYPESnumeric_add@Base 0 PGTYPESnumeric_cmp@Base 0 PGTYPESnumeric_copy@Base 0 PGTYPESnumeric_div@Base 0 PGTYPESnumeric_free@Base 0 PGTYPESnumeric_from_asc@Base 0 PGTYPESnumeric_from_decimal@Base 0 PGTYPESnumeric_from_double@Base 0 PGTYPESnumeric_from_int@Base 0 PGTYPESnumeric_from_long@Base 0 PGTYPESnumeric_mul@Base 0 PGTYPESnumeric_new@Base 0 PGTYPESnumeric_sub@Base 0 PGTYPESnumeric_to_asc@Base 0 PGTYPESnumeric_to_decimal@Base 0 PGTYPESnumeric_to_double@Base 0 PGTYPESnumeric_to_int@Base 0 PGTYPESnumeric_to_long@Base 0 PGTYPEStimestamp_add_interval@Base 0 PGTYPEStimestamp_current@Base 0 PGTYPEStimestamp_defmt_asc@Base 0 PGTYPEStimestamp_defmt_scan@Base 0 PGTYPEStimestamp_fmt_asc@Base 0 PGTYPEStimestamp_from_asc@Base 0 PGTYPEStimestamp_sub@Base 0 PGTYPEStimestamp_sub_interval@Base 0 PGTYPEStimestamp_to_asc@Base 0 debian/postgresql-9.3.postinst0000644000000000000000000000025613334546526013523 0ustar #!/bin/sh set -e VERSION=9.3 if [ "$1" = configure ]; then . /usr/share/postgresql-common/maintscripts-functions configure_version $VERSION "$2" fi #DEBHELPER# debian/rules0000755000000000000000000001243713334546551010266 0ustar #!/usr/bin/make -f ifneq ($(shell which tclsh8.6),) TCL_VER := 8.6 else TCL_VER := 8.5 endif MAJOR_VER := 9.3 DEB_BUILD_ARCH = $(shell dpkg-architecture -qDEB_BUILD_ARCH) # this must also work for old releases with multiarch, so don't fail if the # variable doesn't exist DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH || true) # support multi-arch location ifneq ($(wildcard /usr/lib/$(DEB_HOST_MULTIARCH)/tcl$(TCL_VER)),) TCL_CONFIG_DIR := /usr/lib/$(DEB_HOST_MULTIARCH) else TCL_CONFIG_DIR := /usr/lib endif # support both hardening-wrapper (for backports) and dpkg-buildflags export DEB_BUILD_HARDENING = 1 export DEB_BUILD_MAINT_OPTIONS = hardening=+all,-pie DPKG_EXPORT_BUILDFLAGS = 1 -include /usr/share/dpkg/buildflags.mk LDFLAGS+= -Wl,--as-needed -L/usr/lib/mit-krb5 -L/usr/lib/$(DEB_HOST_MULTIARCH)/mit-krb5 CFLAGS+= -fPIC -pie -I/usr/include/mit-krb5 # When protecting the postmaster with oom_adj=-17, allow the OOM killer to slay # the backends (http://archives.postgresql.org/pgsql-hackers/2010-01/msg00170.php) ifeq ($(shell uname -s),Linux) CFLAGS+= -DLINUX_OOM_SCORE_ADJ=0 endif # sparc and alpha's gcc used to miscompile; see # http://lists.debian.org/debian-alpha/2007/11/msg00025.html #ifneq ($(findstring $(DEB_BUILD_ARCH), sparc alpha),) # CFLAGS+=-O1 #endif # Facilitate hierarchical profile generation on amd64 (#730134) ifeq ($(shell dpkg-architecture -qDEB_BUILD_ARCH),amd64) CFLAGS+= -fno-omit-frame-pointer endif export DPKG_GENSYMBOLS_CHECK_LEVEL=4 COMMON_CONFIGURE_FLAGS= \ --mandir=/usr/share/postgresql/$(MAJOR_VER)/man \ --docdir=/usr/share/doc/postgresql-doc-$(MAJOR_VER) \ --sysconfdir=/etc/postgresql-common \ --datarootdir=/usr/share/ \ --datadir=/usr/share/postgresql/$(MAJOR_VER) \ --bindir=/usr/lib/postgresql/$(MAJOR_VER)/bin \ --libdir=/usr/lib/ \ --libexecdir=/usr/lib/postgresql/ \ --includedir=/usr/include/postgresql/ \ --enable-nls \ --enable-integer-datetimes \ --enable-thread-safety \ --enable-debug \ --disable-rpath \ --with-ossp-uuid \ --with-gnu-ld \ --with-pgport=5432 \ --with-system-tzdata=/usr/share/zoneinfo \ CFLAGS='$(CFLAGS)' \ LDFLAGS='$(LDFLAGS)' # allow missing krb5 and ldap during bootstrapping ifeq ($(DEB_STAGE),stage1) BOOTSTRAP_FLAGS= else BOOTSTRAP_FLAGS= --with-krb5 --with-gssapi --with-ldap endif # build should fail on test suite failures on all arches TESTSUITE_FAIL_CMD=exit 1 # hurd doesn't implement semaphores; succeed anyway so they at least have libpq5 # plperl currently fails on kfreebsd-* ifneq ($(filter $(DEB_BUILD_ARCH), hurd-i386 kfreebsd-amd64 kfreebsd-i386),) TESTSUITE_FAIL_CMD=exit 0 endif %: dh $@ --parallel override_dh_auto_configure: stamp/configure-build stamp/configure-build-py3 stamp/configure-build: mkdir -p stamp build cd build && ../configure \ --with-tcl \ --with-perl \ --with-python \ --with-pam \ --with-openssl \ --with-libxml \ --with-libxslt \ --with-tclconfig=$(TCL_CONFIG_DIR)/tcl$(TCL_VER) \ --with-includes=/usr/include/tcl$(TCL_VER) \ PYTHON=/usr/bin/python \ $(COMMON_CONFIGURE_FLAGS) \ $(BOOTSTRAP_FLAGS) touch "$@" stamp/configure-build-py3: mkdir build-py3 cd build-py3 && ../configure \ --with-python \ PYTHON=/usr/bin/python3 \ $(COMMON_CONFIGURE_FLAGS) touch "$@" override_dh_auto_build: stamp/build stamp/build-py3 stamp/build: stamp/configure-build cd build && $(MAKE) world # generate POT files for translators find -name nls.mk -exec sh -c "make -C \$$(dirname {}) init-po" \; # build tutorial stuff make -C build/src/tutorial NO_PGXS=1 touch "$@" stamp/build-py3: stamp/configure-build-py3 cd build-py3 && $(MAKE) -C src/backend/ submake-errcodes && $(MAKE) -C src/pl/plpython touch "$@" override_dh_auto_install: make -C build-py3/src/pl/plpython install DESTDIR=$(CURDIR)/debian/tmp make -C build install-world DESTDIR=$(CURDIR)/debian/tmp # compress manpages gzip -9n $(CURDIR)/debian/tmp/usr/share/postgresql/*/man/man*/*.[137] override_dh_makeshlibs: dh_makeshlibs -Xusr/lib/postgresql/$(MAJOR_VER) override_dh_auto_clean: rm -rf build* stamp contrib/file_fdw/sql/file_fdw.sql override_dh_installchangelogs: dh_installchangelogs HISTORY override_dh_compress: dh_compress -X.source -X.c override_dh_install: dh_install --fail-missing # these get installed into the individual -/l* packages; -f because it # does not exist for an -A build rm -f debian/postgresql-contrib-$(MAJOR_VER)/usr/share/postgresql/$(MAJOR_VER)/extension/pl* if [ -d debian/postgresql-doc-$(MAJOR_VER) ]; then \ install src/tutorial/*.c src/tutorial/*.source src/tutorial/Makefile src/tutorial/README debian/postgresql-doc-$(MAJOR_VER)/usr/share/doc/postgresql-doc-$(MAJOR_VER)/tutorial; \ fi override_dh_auto_test: ifeq (, $(findstring nocheck, $(DEB_BUILD_OPTIONS))) if ! make -C build check-world EXTRA_REGRESS_OPTS='--port=$(shell perl -le 'print 1024 + int(rand(64000))')'; then \ for l in `find build -name regression.diffs -o -name initdb.log -o -name postmaster.log`; do \ echo "******** $$l ********"; \ tail -n100 $$l; \ done; \ $(TESTSUITE_FAIL_CMD); \ fi endif override_dh_strip: dh_strip --dbg-package=postgresql-$(MAJOR_VER)-dbg override_dh_builddeb: dh_builddeb -- -Zxz debian/postgresql-client-9.3.prerm0000644000000000000000000000025013334546526014233 0ustar #!/bin/sh set -e #DEBHELPER# VERSION=9.3 if [ "$1" = remove ]; then . /usr/share/postgresql-common/maintscripts-functions remove_client_version $VERSION fi debian/postgresql-plpython3-9.3.install0000644000000000000000000000012613334546526015240 0ustar usr/lib/postgresql/9.3/lib/plpython3.so usr/share/postgresql/9.3/extension/plpython3* debian/control0000644000000000000000000003064213334546551010607 0ustar Source: postgresql-9.3 Section: database Priority: optional Maintainer: Ubuntu Developers XSBC-Original-Maintainer: Debian PostgreSQL Maintainers Uploaders: Martin Pitt , Peter Eisentraut , Christoph Berg Standards-Version: 3.9.5 Build-Depends: debhelper (>= 8~), dpkg-dev (>= 1.16.1~) | hardening-wrapper, perl (>= 5.8), libperl-dev, tcl8.6-dev | tcl8.5-dev, libedit-dev, libssl-dev, zlib1g-dev | libz-dev, libpam0g-dev | libpam-dev, libxml2-dev, krb5-multidev, libldap2-dev, libxslt1-dev, libossp-uuid-dev, python-dev, python3-dev, bison, flex, openjade, docbook-dsssl, docbook-xsl, docbook, opensp, xsltproc, gettext Homepage: http://www.postgresql.org/ Vcs-Browser: http://anonscm.debian.org/loggerhead/pkg-postgresql/postgresql-9.3/trunk Vcs-Bzr: http://bzr.debian.org/bzr/pkg-postgresql/postgresql-9.3/trunk/ XS-Testsuite: autopkgtest Package: libpq-dev Architecture: any Section: libdevel Depends: ${misc:Depends}, ${shlibs:Depends}, libpq5 (= ${binary:Version}), libssl-dev, krb5-multidev, comerr-dev Suggests: postgresql-doc-9.3 Description: header files for libpq5 (PostgreSQL library) Header files and static library for compiling C programs to link with the libpq library in order to communicate with a PostgreSQL database backend. . PostgreSQL is an object-relational SQL database management system. Package: libpq5 Architecture: any Section: libs Depends: ${misc:Depends}, ${shlibs:Depends} Description: PostgreSQL C client library libpq is a C library that enables user programs to communicate with the PostgreSQL database server. The server can be on another machine and accessed through TCP/IP. This version of libpq is compatible with servers from PostgreSQL 8.2 or later. . This package contains the run-time library, needed by packages using libpq. . PostgreSQL is an object-relational SQL database management system. Package: libecpg6 Architecture: any Section: libs Depends: ${misc:Depends}, ${shlibs:Depends} Description: run-time library for ECPG programs The libecpg shared library is used by programs built with ECPG (Embedded PostgreSQL for C). . PostgreSQL is an object-relational SQL database management system. Package: libecpg-dev Architecture: any Section: libdevel Depends: ${misc:Depends}, ${shlibs:Depends}, libpq-dev, libecpg6 (= ${binary:Version}), libecpg-compat3 (= ${binary:Version}), libpgtypes3 (= ${binary:Version}) Description: development files for ECPG (Embedded PostgreSQL for C) This package contains the necessary files to build ECPG (Embedded PostgreSQL for C) programs. It includes the development libraries and the preprocessor program ecpg. . PostgreSQL is an object-relational SQL database management system. . Install this package if you want to write C programs with SQL statements embedded in them (rather than run by an external process). Package: libecpg-compat3 Architecture: any Section: libs Depends: ${misc:Depends}, ${shlibs:Depends} Description: older version of run-time library for ECPG programs The libecpg_compat shared library is used by programs built with ecpg. (Embedded PostgreSQL for C). . PostgreSQL is an object-relational SQL database management system. Package: libpgtypes3 Architecture: any Section: libs Depends: ${misc:Depends}, ${shlibs:Depends} Description: shared library libpgtypes for PostgreSQL 9.3 The libpgtypes shared library is used by programs built with ecpg. (Embedded PostgreSQL for C). . PostgreSQL is an object-relational SQL database management system. Package: postgresql-9.3 Architecture: any Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-client-9.3, postgresql-common (>= 142~), tzdata, ssl-cert, locales Suggests: oidentd | ident-server, locales-all Description: object-relational SQL database, version 9.3 server PostgreSQL is a fully featured object-relational database management system. It supports a large part of the SQL standard and is designed to be extensible by users in many aspects. Some of the features are: ACID transactions, foreign keys, views, sequences, subqueries, triggers, user-defined types and functions, outer joins, multiversion concurrency control. Graphical user interfaces and bindings for many programming languages are available as well. . This package provides the database server for PostgreSQL 9.3. Servers for other major release versions can be installed simultaneously and are coordinated by the postgresql-common package. A package providing ident-server is needed if you want to authenticate remote connections with identd. Package: postgresql-9.3-dbg Section: debug Priority: extra Architecture: any Depends: ${misc:Depends}, postgresql-9.3 (= ${binary:Version}) Conflicts: postgresql-dbg, postgresql-9.1-dbg Provides: postgresql-dbg Replaces: postgresql-9.1-dbg Description: debug symbols for postgresql-9.3 PostgreSQL is a fully featured object-relational database management system. It supports a large part of the SQL standard and is designed to be extensible by users in many aspects. Some of the features are: ACID transactions, foreign keys, views, sequences, subqueries, triggers, user-defined types and functions, outer joins, multiversion concurrency control. Graphical user interfaces and bindings for many programming languages are available as well. . This package provides detached debugging symbols for PostgreSQL 9.3. Package: postgresql-client-9.3 Architecture: any Depends: ${misc:Depends}, ${shlibs:Depends}, libpq5 (>= ${source:Upstream-Version}), postgresql-client-common (>= 142~) Suggests: postgresql-9.3, postgresql-doc-9.3 Provides: postgresql-client Description: front-end programs for PostgreSQL 9.3 This package contains client and administrative programs for PostgreSQL: these are the interactive terminal client psql and programs for creating and removing users and databases. . This is the client package for PostgreSQL 9.3. If you install PostgreSQL 9.3 on a standalone machine, you need the server package postgresql-9.3, too. On a network, you can install this package on many client machines, while the server package may be installed on only one machine. . PostgreSQL is an object-relational SQL database management system. Package: postgresql-server-dev-9.3 Architecture: any Section: libdevel Depends: ${misc:Depends}, ${shlibs:Depends}, libpq-dev (>= 9.3~), postgresql-common (>= 142~) Description: development files for PostgreSQL 9.3 server-side programming Header files for compiling SSI code to link into PostgreSQL's backend; for example, for C functions to be called from SQL. . This package also contains the Makefiles necessary for building add-on modules of PostgreSQL, which would otherwise have to be built in the PostgreSQL source-code tree. . PostgreSQL is an object-relational SQL database management system. Package: postgresql-doc-9.3 Architecture: all Section: doc Depends: ${misc:Depends} Description: documentation for the PostgreSQL database management system This package contains all README files, user manual, and examples for PostgreSQL 9.3. The manual is in HTML format. . PostgreSQL is an object-relational SQL database management system. Package: postgresql-contrib-9.3 Architecture: any Depends: postgresql-9.3 (= ${binary:Version}), ${misc:Depends}, ${shlibs:Depends} Suggests: libdbd-pg-perl Description: additional facilities for PostgreSQL The PostgreSQL contrib package provides several additional features for the PostgreSQL database. This version is built to work with the server package postgresql-9.3. contrib often serves as a testbed for features before they are adopted into PostgreSQL proper: . adminpack - File and log manipulation routines, used by pgAdmin btree_gist - B-Tree indexing using GiST (Generalised Search Tree) chkpass - An auto-encrypted password datatype cube - Multidimensional-cube datatype (GiST indexing example) dblink - Functions to return results from a remote database earthdistance - Operator for computing the distance (in miles) between two points on the earth's surface fuzzystrmatch - Levenshtein, metaphone, and soundex fuzzy string matching hstore - Store (key, value) pairs intagg - Integer aggregator/enumerator _int - Index support for arrays of int4, using GiST (benchmark needs the libdbd-pg-perl package) isn - type extensions for ISBN, ISSN, ISMN, EAN13 product numbers lo - Large Object maintenance ltree - Tree-like data structures oid2name - Maps OIDs to table names pageinspect - Inspection of database pages passwordcheck - Simple password strength checker pg_buffercache - Real time queries on the shared buffer cache pg_freespacemap- Displays the contents of the free space map (FSM) pg_trgm - Determine the similarity of text based on trigram matching pg_standby - Create a warm stand-by server pgbench - TPC-B like benchmark pgcrypto - Cryptographic functions pgrowlocks - A function to return row locking information pgstattuple - Returns the percentage of dead tuples in a table; this indicates whether a vacuum is required. postgresql_fwd - foreign data wrapper for PostgreSQL seg - Confidence-interval datatype (GiST indexing example) spi - PostgreSQL Server Programming Interface; 4 examples of its use: autoinc - A function for implementing AUTOINCREMENT/ IDENTITY insert_username - function for inserting user names moddatetime - Update modification timestamps refint - Functions for implementing referential integrity (foreign keys). Note that this is now superseded by built-in referential integrity. timetravel - Re-implements in user code the time travel feature that was removed in 6.3. tablefunc - examples of functions returning tables uuid-ossp - UUID generation functions vacuumlo - Remove orphaned large objects . PostgreSQL is an object-relational SQL database management system. Package: postgresql-plperl-9.3 Architecture: any Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-9.3 (= ${binary:Version}), perl Provides: postgresql-plperl Description: PL/Perl procedural language for PostgreSQL 9.3 PL/Perl enables an SQL developer to write procedural language functions for PostgreSQL 9.3 in Perl. You need this package if you have any PostgreSQL 9.3 functions that use the languages plperl or plperlu. . PostgreSQL is an object-relational SQL database management system. Package: postgresql-plpython-9.3 Architecture: any Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-9.3 (= ${binary:Version}) Provides: postgresql-plpython Description: PL/Python procedural language for PostgreSQL 9.3 PL/Python enables an SQL developer to write procedural language functions for PostgreSQL 9.3 in Python. You need this package if you have any PostgreSQL 9.3 functions that use the languages plpython or plpythonu. . PostgreSQL is an object-relational SQL database management system. Package: postgresql-plpython3-9.3 Architecture: any Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-9.3 (= ${binary:Version}) Replaces: postgresql-plpython-9.3 (<< ${binary:Version}) Breaks: postgresql-plpython-9.3 (<< ${binary:Version}) Provides: postgresql-plpython3 Description: PL/Python 3 procedural language for PostgreSQL 9.3 PL/Python 3 enables an SQL developer to write procedural language functions for PostgreSQL 9.3 in Python 3. You need this package if you have any PostgreSQL 9.3 functions that use the languages plpython3 or plpython3u. . PostgreSQL is an object-relational SQL database management system. Package: postgresql-pltcl-9.3 Architecture: any Depends: ${misc:Depends}, ${shlibs:Depends}, postgresql-9.3 (= ${binary:Version}) Provides: postgresql-pltcl Description: PL/Tcl procedural language for PostgreSQL 9.3 PL/Tcl enables an SQL developer to write procedural language functions for PostgreSQL 9.3 in Tcl. You need this package if you have any PostgreSQL 9.3 functions that use the languages pltcl or pltclu. . PostgreSQL is an object-relational SQL database management system. debian/watch0000644000000000000000000000022313334546526010227 0ustar version=3 opts=uversionmangle=s/alpha/~alpha/;s/beta/~beta/;s/rc/~rc/ \ ftp://ftp.postgresql.org/pub/source/v(9\.3.*)/postgresql-(9\.3.*).tar.bz2 debian/postgresql-9.3.links0000644000000000000000000000014113334546526012751 0ustar /usr/share/doc/postgresql-common/README.Debian.gz /usr/share/doc/postgresql-9.3/README.Debian.gz debian/postgresql-9.3.prerm0000644000000000000000000000026613334546526012766 0ustar #!/bin/sh set -e VERSION=9.3 #DEBHELPER# . /usr/share/postgresql-common/maintscripts-functions stop_version $VERSION if [ "$1" = remove ]; then remove_version $VERSION fi debian/libecpg6.install0000644000000000000000000000006513334546551012263 0ustar usr/lib/libecpg.so.6* /usr/share/locale/*/*/ecpg*.mo debian/patches/0000755000000000000000000000000013334546551010626 5ustar debian/patches/02-relax-sslkey-permscheck.patch0000644000000000000000000000260013334546526016633 0ustar Description: Relax security check on private SSL key file: The file is also considered safe if it has owner and/or group "root", and if it is group-readable (unless the group is something other than root or the database owner group). Author: Martin Pitt Forwarded: Yes, but rejected upstream Bug-Debian: http://bugs.debian.org/3279.2 Index: postgresql-9.2/src/backend/libpq/be-secure.c =================================================================== --- postgresql-9.2.orig/src/backend/libpq/be-secure.c 2012-05-11 00:35:09.000000000 +0200 +++ postgresql-9.2/src/backend/libpq/be-secure.c 2012-05-15 07:39:50.557598618 +0200 @@ -768,12 +768,15 @@ * directory permission check in postmaster.c) */ #if !defined(WIN32) && !defined(__CYGWIN__) - if (!S_ISREG(buf.st_mode) || buf.st_mode & (S_IRWXG | S_IRWXO)) + if (!S_ISREG(buf.st_mode) || (buf.st_mode & (S_IWGRP | S_IRWXO)) || + ((buf.st_uid != geteuid()) && buf.st_uid != 0)) ereport(FATAL, (errcode(ERRCODE_CONFIG_FILE_ERROR), errmsg("private key file \"%s\" has group or world access", ssl_key_file), - errdetail("Permissions should be u=rw (0600) or less."))); + errdetail("File must be owned by the \ +database user or root, must have no write permission for \"group\", and must \ +have no permissions for \"other\"."))); #endif if (SSL_CTX_use_PrivateKey_file(SSL_context, debian/patches/53-pg_service.conf_directory_doc.patch0000644000000000000000000000166413334546526020070 0ustar Author: Martin Pitt Description: Update pg_service.conf example to tell the Debian specific file location. Forwarded: No, Debian specific Index: postgresql-9.2-9.2~beta1/src/interfaces/libpq/pg_service.conf.sample =================================================================== --- postgresql-9.2-9.2~beta1.orig/src/interfaces/libpq/pg_service.conf.sample 2011-04-27 23:17:22.000000000 +0200 +++ postgresql-9.2-9.2~beta1/src/interfaces/libpq/pg_service.conf.sample 2011-05-10 11:25:42.151949794 +0200 @@ -8,8 +8,8 @@ # to look up such parameters. A sample configuration for postgres is # included in this file. Lines beginning with '#' are comments. # -# Copy this to your sysconf directory (typically /usr/local/pgsql/etc) and -# rename it pg_service.conf. +# Copy this to /etc/postgresql-common/ (or select its location with the +# PGSYSCONFDIR environment variable) and rename it pg_service.conf. # # #[postgres] debian/patches/series0000644000000000000000000000047013334546526012046 0ustar 00git-vpath.patch 00git-vpath2.patch 01-vpath3.patch 02-relax-sslkey-permscheck.patch 03-config-update.patch 50-per-version-dirs.patch 51-default-sockets-in-var.patch 52-tutorial-README.patch 53-pg_service.conf_directory_doc.patch 54-debian-alternatives-for-external-tools.patch 64-pg_upgrade-sockdir 70-history debian/patches/51-default-sockets-in-var.patch0000644000000000000000000000200513334546526016360 0ustar Author: Martin Pitt Description: Put server Unix sockets into /var/run/postgresql/ by default Forwarded: No, Debian specific configuration with postgresql-common Using /tmp for sockets allows everyone to spoof a PostgreSQL server. Thus use /var/run/postgresql/ for "system" clusters which run as 'postgres' (user clusters will still use /tmp). Since system cluster are by far the common case, set it as default. Index: postgresql-9.2/src/include/pg_config_manual.h =================================================================== --- postgresql-9.2.orig/src/include/pg_config_manual.h 2012-05-11 00:35:09.000000000 +0200 +++ postgresql-9.2/src/include/pg_config_manual.h 2012-05-15 07:40:07.853599455 +0200 @@ -144,7 +144,7 @@ * here's where to twiddle it. You can also override this at runtime * with the postmaster's -k switch. */ -#define DEFAULT_PGSOCKET_DIR "/tmp" +#define DEFAULT_PGSOCKET_DIR "/var/run/postgresql" /* * The random() function is expected to yield values between 0 and debian/patches/64-pg_upgrade-sockdir0000644000000000000000000000141613334546526014555 0ustar Fix for: connection to database failed: Unix-domain socket path "/build/buildd-postgresql-9.3_9.3~beta1-1-i386-mHjRUH/postgresql-9.3-9.3~beta1/build/contrib/pg_upgrade/.s.PGSQL.50432" is too long (maximum 107 bytes) See also: http://lists.debian.org/debian-wb-team/2013/05/msg00015.html --- a/contrib/pg_upgrade/option.c +++ b/contrib/pg_upgrade/option.c @@ -411,6 +411,11 @@ get_sock_dir(ClusterInfo *cluster, bool cluster->sockdir = pg_malloc(MAXPGPATH); if (!getcwd(cluster->sockdir, MAXPGPATH)) pg_log(PG_FATAL, "cannot find current directory\n"); +#ifndef UNIX_PATH_MAX +#define UNIX_PATH_MAX 108 +#endif + if (strlen(cluster->sockdir) > UNIX_PATH_MAX - sizeof(".s.PGSQL.50432")) + strcpy(cluster->sockdir, "/tmp"); /* fall back to tmp */ } else { debian/patches/52-tutorial-README.patch0000644000000000000000000000152013334546526014671 0ustar Author: Martin Pitt Description: Update tutorial README for required build dependencies. Forwarded: No, Debian specific Index: postgresql-9.0-9.0~beta1/src/tutorial/README =================================================================== --- postgresql-9.0-9.0~beta1.orig/src/tutorial/README 2008-03-21 14:23:29.000000000 +0100 +++ postgresql-9.0-9.0~beta1/src/tutorial/README 2010-05-01 15:01:42.747229787 +0200 @@ -6,8 +6,7 @@ This directory contains SQL tutorial scripts. To look at them, first do a % make to compile all the scripts and C files for the user-defined functions -and types. (make needs to be GNU make --- it may be named something -different on your system, often gmake) +and types. This requires postgresql-server-dev-9.2 to be installed. Then, run psql with the -s (single-step) flag: % psql -s debian/patches/54-debian-alternatives-for-external-tools.patch0000644000000000000000000000234513334546526021566 0ustar Author: Martin Pitt Description: Use Debian alternatives for external tools instead of hardcoded programs Forwarded: No, Debian specific Index: postgresql-9.2/src/bin/psql/print.h =================================================================== --- postgresql-9.2.orig/src/bin/psql/print.h 2012-05-11 00:35:09.000000000 +0200 +++ postgresql-9.2/src/bin/psql/print.h 2012-05-15 07:40:14.641599783 +0200 @@ -178,7 +178,7 @@ extern const printTextFormat *get_line_style(const printTableOpt *opt); #ifndef __CYGWIN__ -#define DEFAULT_PAGER "more" +#define DEFAULT_PAGER "/usr/bin/pager" #else #define DEFAULT_PAGER "less" #endif Index: postgresql-9.2/src/bin/psql/settings.h =================================================================== --- postgresql-9.2.orig/src/bin/psql/settings.h 2012-05-11 00:35:09.000000000 +0200 +++ postgresql-9.2/src/bin/psql/settings.h 2012-05-15 07:40:14.645599783 +0200 @@ -19,8 +19,8 @@ #define DEFAULT_EDITOR "notepad.exe" /* no DEFAULT_EDITOR_LINENUMBER_ARG for Notepad */ #else -#define DEFAULT_EDITOR "vi" -#define DEFAULT_EDITOR_LINENUMBER_ARG "+" +#define DEFAULT_EDITOR "sensible-editor" +/*#define DEFAULT_EDITOR_LINENUMBER_ARG "+"*/ #endif #define DEFAULT_PROMPT1 "%/%R%# " debian/patches/70-history0000644000000000000000000000054113334546526012500 0ustar --- a/HISTORY +++ b/HISTORY @@ -3,3 +3,6 @@ Distribution file sets include release notes for their version and preceding versions. Visit the file doc/src/sgml/html/release.html in an HTML browser. + +On Debian systems, the release notes are contained in the postgresql-doc-* +packages, located in /usr/share/doc/postgresql-doc-*/html/release.html. debian/patches/01-vpath3.patch0000644000000000000000000000221113334546526013270 0ustar Make the install targets depend on installdirs (not yet upstream, tbd) --- a/src/makefiles/pgxs.mk +++ b/src/makefiles/pgxs.mk @@ -132,29 +132,29 @@ $(INSTALL_PROGRAM) $(PROGRAM)$(X) '$(DESTDIR)$(bindir)' endif # PROGRAM -installcontrol: $(addsuffix .control, $(EXTENSION)) +installcontrol: $(addsuffix .control, $(EXTENSION)) | installdirs ifneq (,$(EXTENSION)) $(INSTALL_DATA) $^ '$(DESTDIR)$(datadir)/extension/' endif -installdata: $(DATA) $(DATA_built) +installdata: $(DATA) $(DATA_built) | installdirs ifneq (,$(DATA)$(DATA_built)) $(INSTALL_DATA) $^ '$(DESTDIR)$(datadir)/$(datamoduledir)/' endif -installdatatsearch: $(DATA_TSEARCH) +installdatatsearch: $(DATA_TSEARCH) | installdirs ifneq (,$(DATA_TSEARCH)) $(INSTALL_DATA) $^ '$(DESTDIR)$(datadir)/tsearch_data/' endif -installdocs: $(DOCS) +installdocs: $(DOCS) | installdirs ifdef DOCS ifdef docdir $(INSTALL_DATA) $^ '$(DESTDIR)$(docdir)/$(docmoduledir)/' endif # docdir endif # DOCS -installscripts: $(SCRIPTS) $(SCRIPTS_built) +installscripts: $(SCRIPTS) $(SCRIPTS_built) | installdirs ifdef SCRIPTS $(INSTALL_SCRIPT) $^ '$(DESTDIR)$(bindir)/' endif # SCRIPTS debian/patches/50-per-version-dirs.patch0000644000000000000000000000345513334546551015310 0ustar Author: Martin Pitt Description: Use version specific installation directories so that several major versions can be installed in parallel. Forwarded: No, Debian specific packaging with postgresql-common * Install lib files into /usr/lib/postgresql//lib/ * Install server related header files into /usr/include/postgresql//server/ * Disable PostgreSQL's automagic path mangling and fix libdir for pg_config, so that pg_config in /usr/bin and /usr/lib/postgresql//bin behave identically. Bug-Debian: http://bugs.debian.org/462037 --- a/src/Makefile.global.in +++ b/src/Makefile.global.in @@ -99,7 +99,7 @@ pkglibdir = $(libdir) ifeq "$(findstring pgsql, $(pkglibdir))" "" ifeq "$(findstring postgres, $(pkglibdir))" "" -override pkglibdir := $(pkglibdir)/postgresql +override pkglibdir := $(pkglibdir)/postgresql/@PG_MAJORVERSION@/lib endif endif @@ -147,7 +147,7 @@ # These derived path variables aren't separately configurable. -includedir_server = $(pkgincludedir)/server +includedir_server = $(pkgincludedir)/@PG_MAJORVERSION@/server includedir_internal = $(pkgincludedir)/internal pgxsdir = $(pkglibdir)/pgxs --- a/src/bin/pg_config/pg_config.c +++ b/src/bin/pg_config/pg_config.c @@ -26,6 +26,8 @@ #include "port.h" +#include "../port/pg_config_paths.h" + static const char *progname; static char mypath[MAXPGPATH]; @@ -481,7 +483,6 @@ { int i; int j; - int ret; set_pglocale_pgservice(argv[0], PG_TEXTDOMAIN("pg_config")); @@ -497,13 +498,7 @@ } } - ret = find_my_exec(argv[0], mypath); - - if (ret) - { - fprintf(stderr, _("%s: could not find own program executable\n"), progname); - exit(1); - } + snprintf(mypath, sizeof(mypath), "%s/%s", PGBINDIR, progname); /* no arguments -> print everything */ if (argc < 2) debian/patches/00git-vpath2.patch0000644000000000000000000000132413334546526013776 0ustar commit 82b0102650cf85268145a46f0ab488bacf6599a1 Author: Andrew Dunstan Date: Wed Jul 3 19:03:31 2013 -0400 Install all a Makefile's extension controls, not just the first. Bug introduced by commit 6697aa2bc25c83b88d6165340348a31328c35de6 and reported by Robert Haas. diff --git a/src/makefiles/pgxs.mk b/src/makefiles/pgxs.mk index f4eaa74..8618aa1 100644 --- a/src/makefiles/pgxs.mk +++ b/src/makefiles/pgxs.mk @@ -134,7 +134,7 @@ endif # PROGRAM installcontrol: $(addsuffix .control, $(EXTENSION)) ifneq (,$(EXTENSION)) - $(INSTALL_DATA) $< '$(DESTDIR)$(datadir)/extension/' + $(INSTALL_DATA) $^ '$(DESTDIR)$(datadir)/extension/' endif installdata: $(DATA) $(DATA_built) debian/patches/03-config-update.patch0000644000000000000000000002353213334546526014623 0ustar Description: Refresh config.{guess,sub} to latest version for enabling ports. Index: postgresql-9.3-9.3.1/config/config.guess =================================================================== --- postgresql-9.3-9.3.1.orig/config/config.guess 2013-10-08 05:17:38.000000000 +0200 +++ postgresql-9.3-9.3.1/config/config.guess 2013-10-09 06:54:30.454799557 +0200 @@ -2,7 +2,7 @@ # Attempt to guess a canonical system name. # Copyright 1992-2013 Free Software Foundation, Inc. -timestamp='2013-04-24' +timestamp='2013-06-10' # This file is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by @@ -132,6 +132,27 @@ UNAME_SYSTEM=`(uname -s) 2>/dev/null` || UNAME_SYSTEM=unknown UNAME_VERSION=`(uname -v) 2>/dev/null` || UNAME_VERSION=unknown +case "${UNAME_SYSTEM}" in +Linux|GNU|GNU/*) + # If the system lacks a compiler, then just pick glibc. + # We could probably try harder. + LIBC=gnu + + eval $set_cc_for_build + cat <<-EOF > $dummy.c + #include + #if defined(__UCLIBC__) + LIBC=uclibc + #elif defined(__dietlibc__) + LIBC=dietlibc + #else + LIBC=gnu + #endif + EOF + eval `$CC_FOR_BUILD -E $dummy.c 2>/dev/null | grep '^LIBC'` + ;; +esac + # Note: order is significant - the case branches are not exclusive. case "${UNAME_MACHINE}:${UNAME_SYSTEM}:${UNAME_RELEASE}:${UNAME_VERSION}" in @@ -853,21 +874,21 @@ exit ;; *:GNU:*:*) # the GNU system - echo `echo ${UNAME_MACHINE}|sed -e 's,[-/].*$,,'`-unknown-gnu`echo ${UNAME_RELEASE}|sed -e 's,/.*$,,'` + echo `echo ${UNAME_MACHINE}|sed -e 's,[-/].*$,,'`-unknown-${LIBC}`echo ${UNAME_RELEASE}|sed -e 's,/.*$,,'` exit ;; *:GNU/*:*:*) # other systems with GNU libc and userland - echo ${UNAME_MACHINE}-unknown-`echo ${UNAME_SYSTEM} | sed 's,^[^/]*/,,' | tr '[A-Z]' '[a-z]'``echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'`-gnu + echo ${UNAME_MACHINE}-unknown-`echo ${UNAME_SYSTEM} | sed 's,^[^/]*/,,' | tr '[A-Z]' '[a-z]'``echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'`-${LIBC} exit ;; i*86:Minix:*:*) echo ${UNAME_MACHINE}-pc-minix exit ;; aarch64:Linux:*:*) - echo ${UNAME_MACHINE}-unknown-linux-gnu + echo ${UNAME_MACHINE}-unknown-linux-${LIBC} exit ;; aarch64_be:Linux:*:*) UNAME_MACHINE=aarch64_be - echo ${UNAME_MACHINE}-unknown-linux-gnu + echo ${UNAME_MACHINE}-unknown-linux-${LIBC} exit ;; alpha:Linux:*:*) case `sed -n '/^cpu model/s/^.*: \(.*\)/\1/p' < /proc/cpuinfo` in @@ -880,67 +901,54 @@ EV68*) UNAME_MACHINE=alphaev68 ;; esac objdump --private-headers /bin/sh | grep -q ld.so.1 - if test "$?" = 0 ; then LIBC="libc1" ; else LIBC="" ; fi - echo ${UNAME_MACHINE}-unknown-linux-gnu${LIBC} + if test "$?" = 0 ; then LIBC="gnulibc1" ; fi + echo ${UNAME_MACHINE}-unknown-linux-${LIBC} exit ;; arc:Linux:*:* | arceb:Linux:*:*) - echo ${UNAME_MACHINE}-unknown-linux-gnu + echo ${UNAME_MACHINE}-unknown-linux-${LIBC} exit ;; arm*:Linux:*:*) eval $set_cc_for_build if echo __ARM_EABI__ | $CC_FOR_BUILD -E - 2>/dev/null \ | grep -q __ARM_EABI__ then - echo ${UNAME_MACHINE}-unknown-linux-gnu + echo ${UNAME_MACHINE}-unknown-linux-${LIBC} else if echo __ARM_PCS_VFP | $CC_FOR_BUILD -E - 2>/dev/null \ | grep -q __ARM_PCS_VFP then - echo ${UNAME_MACHINE}-unknown-linux-gnueabi + echo ${UNAME_MACHINE}-unknown-linux-${LIBC}eabi else - echo ${UNAME_MACHINE}-unknown-linux-gnueabihf + echo ${UNAME_MACHINE}-unknown-linux-${LIBC}eabihf fi fi exit ;; avr32*:Linux:*:*) - echo ${UNAME_MACHINE}-unknown-linux-gnu + echo ${UNAME_MACHINE}-unknown-linux-${LIBC} exit ;; cris:Linux:*:*) - echo ${UNAME_MACHINE}-axis-linux-gnu + echo ${UNAME_MACHINE}-axis-linux-${LIBC} exit ;; crisv32:Linux:*:*) - echo ${UNAME_MACHINE}-axis-linux-gnu + echo ${UNAME_MACHINE}-axis-linux-${LIBC} exit ;; frv:Linux:*:*) - echo ${UNAME_MACHINE}-unknown-linux-gnu + echo ${UNAME_MACHINE}-unknown-linux-${LIBC} exit ;; hexagon:Linux:*:*) - echo ${UNAME_MACHINE}-unknown-linux-gnu + echo ${UNAME_MACHINE}-unknown-linux-${LIBC} exit ;; i*86:Linux:*:*) - LIBC=gnu - eval $set_cc_for_build - sed 's/^ //' << EOF >$dummy.c - #ifdef __dietlibc__ - LIBC=dietlibc - #endif - #else - #include - #ifdef __UCLIBC__ - LIBC=uclibc - #endif -EOF - eval `$CC_FOR_BUILD -E $dummy.c 2>/dev/null | grep '^LIBC'` - echo "${UNAME_MACHINE}-pc-linux-${LIBC}" + echo ${UNAME_MACHINE}-pc-linux-${LIBC} exit ;; ia64:Linux:*:*) - echo ${UNAME_MACHINE}-unknown-linux-gnu + echo ${UNAME_MACHINE}-unknown-linux-${LIBC} exit ;; m32r*:Linux:*:*) - echo ${UNAME_MACHINE}-unknown-linux-gnu + echo ${UNAME_MACHINE}-unknown-linux-${LIBC} exit ;; m68*:Linux:*:*) - echo ${UNAME_MACHINE}-unknown-linux-gnu + echo ${UNAME_MACHINE}-unknown-linux-${LIBC} exit ;; mips:Linux:*:* | mips64:Linux:*:*) eval $set_cc_for_build @@ -959,59 +967,63 @@ #endif EOF eval `$CC_FOR_BUILD -E $dummy.c 2>/dev/null | grep '^CPU'` - test x"${CPU}" != x && { echo "${CPU}-unknown-linux-gnu"; exit; } + test x"${CPU}" != x && { echo "${CPU}-unknown-linux-${LIBC}"; exit; } ;; or1k:Linux:*:*) - echo ${UNAME_MACHINE}-unknown-linux-gnu + echo ${UNAME_MACHINE}-unknown-linux-${LIBC} exit ;; or32:Linux:*:*) - echo ${UNAME_MACHINE}-unknown-linux-gnu + echo ${UNAME_MACHINE}-unknown-linux-${LIBC} exit ;; padre:Linux:*:*) - echo sparc-unknown-linux-gnu + echo sparc-unknown-linux-${LIBC} exit ;; parisc64:Linux:*:* | hppa64:Linux:*:*) - echo hppa64-unknown-linux-gnu + echo hppa64-unknown-linux-${LIBC} exit ;; parisc:Linux:*:* | hppa:Linux:*:*) # Look for CPU level case `grep '^cpu[^a-z]*:' /proc/cpuinfo 2>/dev/null | cut -d' ' -f2` in - PA7*) echo hppa1.1-unknown-linux-gnu ;; - PA8*) echo hppa2.0-unknown-linux-gnu ;; - *) echo hppa-unknown-linux-gnu ;; + PA7*) echo hppa1.1-unknown-linux-${LIBC} ;; + PA8*) echo hppa2.0-unknown-linux-${LIBC} ;; + *) echo hppa-unknown-linux-${LIBC} ;; esac exit ;; ppc64:Linux:*:*) - echo powerpc64-unknown-linux-gnu + echo powerpc64-unknown-linux-${LIBC} exit ;; ppc:Linux:*:*) - echo powerpc-unknown-linux-gnu + echo powerpc-unknown-linux-${LIBC} + exit ;; + ppc64le:Linux:*:*) + echo powerpc64le-unknown-linux-${LIBC} + exit ;; + ppcle:Linux:*:*) + echo powerpcle-unknown-linux-${LIBC} exit ;; s390:Linux:*:* | s390x:Linux:*:*) - echo ${UNAME_MACHINE}-ibm-linux + echo ${UNAME_MACHINE}-ibm-linux-${LIBC} exit ;; sh64*:Linux:*:*) - echo ${UNAME_MACHINE}-unknown-linux-gnu + echo ${UNAME_MACHINE}-unknown-linux-${LIBC} exit ;; sh*:Linux:*:*) - echo ${UNAME_MACHINE}-unknown-linux-gnu + echo ${UNAME_MACHINE}-unknown-linux-${LIBC} exit ;; sparc:Linux:*:* | sparc64:Linux:*:*) - echo ${UNAME_MACHINE}-unknown-linux-gnu + echo ${UNAME_MACHINE}-unknown-linux-${LIBC} exit ;; tile*:Linux:*:*) - echo ${UNAME_MACHINE}-unknown-linux-gnu + echo ${UNAME_MACHINE}-unknown-linux-${LIBC} exit ;; vax:Linux:*:*) - echo ${UNAME_MACHINE}-dec-linux-gnu + echo ${UNAME_MACHINE}-dec-linux-${LIBC} exit ;; x86_64:Linux:*:*) - LIBC=gnu - test -r /lib/libc.so && od -An -S13 /lib/libc.so | grep -q __uClibc_main && LIBC=uclibc echo ${UNAME_MACHINE}-unknown-linux-${LIBC} exit ;; xtensa*:Linux:*:*) - echo ${UNAME_MACHINE}-unknown-linux-gnu + echo ${UNAME_MACHINE}-unknown-linux-${LIBC} exit ;; i*86:DYNIX/ptx:4*:*) # ptx 4.0 does uname -s correctly, with DYNIX/ptx in there. @@ -1244,19 +1256,21 @@ exit ;; *:Darwin:*:*) UNAME_PROCESSOR=`uname -p` || UNAME_PROCESSOR=unknown - case $UNAME_PROCESSOR in - i386) - eval $set_cc_for_build - if [ "$CC_FOR_BUILD" != 'no_compiler_found' ]; then - if (echo '#ifdef __LP64__'; echo IS_64BIT_ARCH; echo '#endif') | \ - (CCOPTS= $CC_FOR_BUILD -E - 2>/dev/null) | \ - grep IS_64BIT_ARCH >/dev/null - then - UNAME_PROCESSOR="x86_64" - fi - fi ;; - unknown) UNAME_PROCESSOR=powerpc ;; - esac + eval $set_cc_for_build + if test "$UNAME_PROCESSOR" = unknown ; then + UNAME_PROCESSOR=powerpc + fi + if [ "$CC_FOR_BUILD" != 'no_compiler_found' ]; then + if (echo '#ifdef __LP64__'; echo IS_64BIT_ARCH; echo '#endif') | \ + (CCOPTS= $CC_FOR_BUILD -E - 2>/dev/null) | \ + grep IS_64BIT_ARCH >/dev/null + then + case $UNAME_PROCESSOR in + i386) UNAME_PROCESSOR=x86_64 ;; + powerpc) UNAME_PROCESSOR=powerpc64 ;; + esac + fi + fi echo ${UNAME_PROCESSOR}-apple-darwin${UNAME_RELEASE} exit ;; *:procnto*:*:* | *:QNX:[0123456789]*:*) Index: postgresql-9.3-9.3.1/config/config.sub =================================================================== --- postgresql-9.3-9.3.1.orig/config/config.sub 2013-10-08 05:17:38.000000000 +0200 +++ postgresql-9.3-9.3.1/config/config.sub 2013-10-09 06:54:30.458799557 +0200 @@ -2,7 +2,7 @@ # Configuration validation subroutine script. # Copyright 1992-2013 Free Software Foundation, Inc. -timestamp='2013-04-24' +timestamp='2013-08-10' # This file is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by @@ -257,7 +257,7 @@ | avr | avr32 \ | be32 | be64 \ | bfin \ - | c4x | clipper \ + | c4x | c8051 | clipper \ | d10v | d30v | dlx | dsp16xx \ | epiphany \ | fido | fr30 | frv \ @@ -372,7 +372,7 @@ | be32-* | be64-* \ | bfin-* | bs2000-* \ | c[123]* | c30-* | [cjt]90-* | c4x-* \ - | clipper-* | craynv-* | cydra-* \ + | c8051-* | clipper-* | craynv-* | cydra-* \ | d10v-* | d30v-* | dlx-* \ | elxsi-* \ | f30[01]-* | f700-* | fido-* | fr30-* | frv-* | fx80-* \ @@ -794,7 +794,7 @@ os=-mingw64 ;; mingw32) - basic_machine=i386-pc + basic_machine=i686-pc os=-mingw32 ;; mingw32ce) @@ -830,7 +830,7 @@ basic_machine=`echo $basic_machine | sed -e 's/ms1-/mt-/'` ;; msys) - basic_machine=i386-pc + basic_machine=i686-pc os=-msys ;; mvs) @@ -1546,6 +1546,9 @@ c4x-* | tic4x-*) os=-coff ;; + c8051-*) + os=-elf + ;; hexagon-*) os=-elf ;; debian/patches/00git-vpath.patch0000644000000000000000000001023613334546526013716 0ustar commit 6697aa2bc25c83b88d6165340348a31328c35de6 Author: Andrew Dunstan Date: Mon Jul 1 12:53:05 2013 -0400 Improve support for building PGXS modules with VPATH. A VPATH build will be performed when the module's make file path is not the current directory or when USE_VPATH is set. This will assist packagers and others who prefer to build without polluting the source directories. There is still a bit of work to do here, notably documentation, but it's probably a good idea to commit what we have so far and let people test it out on their modules. Cédric Villemain, with an addition from me. --- a/src/Makefile.global.in +++ b/src/Makefile.global.in @@ -415,13 +415,23 @@ libpq_pgport = -L$(top_builddir)/src/por -L$(top_builddir)/src/common -lpgcommon $(libpq) endif - +# If PGXS is not defined, build libpq and libpgport dependancies as required. +# If the build is with PGXS, then these are supposed to be already built and +# installed, and we just ensure that the expected files exist. +ifndef PGXS submake-libpq: $(MAKE) -C $(libpq_builddir) all +else +submake-libpq: $(libdir)/libpq.so ; +endif +ifndef PGXS submake-libpgport: $(MAKE) -C $(top_builddir)/src/port all $(MAKE) -C $(top_builddir)/src/common all +else +submake-libpgport: $(libdir)/libpgport.a $(libdir)/libpgcommon.a ; +endif .PHONY: submake-libpq submake-libpgport --- a/src/makefiles/pgxs.mk +++ b/src/makefiles/pgxs.mk @@ -62,8 +62,20 @@ top_builddir := $(dir $(PGXS))../.. include $(top_builddir)/src/Makefile.global top_srcdir = $(top_builddir) +# If USE_VPATH is set or Makefile is not in current directory we are building +# the extension with VPATH so we set the variable here +ifdef USE_VPATH +srcdir = $(USE_VPATH) +VPATH = $(USE_VPATH) +else +ifeq ($(CURDIR),$(dir $(firstword $(MAKEFILE_LIST)))) srcdir = . VPATH = +else +srcdir = $(dir $(firstword $(MAKEFILE_LIST))) +VPATH = $(srcdir) +endif +endif # These might be set in Makefile.global, but if they were not found # during the build of PostgreSQL, supply default values so that users @@ -112,33 +124,40 @@ all: all-lib endif # MODULE_big -install: all installdirs -ifneq (,$(EXTENSION)) - $(INSTALL_DATA) $(addprefix $(srcdir)/, $(addsuffix .control, $(EXTENSION))) '$(DESTDIR)$(datadir)/extension/' -endif # EXTENSION -ifneq (,$(DATA)$(DATA_built)) - $(INSTALL_DATA) $(addprefix $(srcdir)/, $(DATA)) $(DATA_built) '$(DESTDIR)$(datadir)/$(datamoduledir)/' -endif # DATA -ifneq (,$(DATA_TSEARCH)) - $(INSTALL_DATA) $(addprefix $(srcdir)/, $(DATA_TSEARCH)) '$(DESTDIR)$(datadir)/tsearch_data/' -endif # DATA_TSEARCH +install: all installdirs installcontrol installdata installdatatsearch installdocs installscripts ifdef MODULES $(INSTALL_SHLIB) $(addsuffix $(DLSUFFIX), $(MODULES)) '$(DESTDIR)$(pkglibdir)/' endif # MODULES +ifdef PROGRAM + $(INSTALL_PROGRAM) $(PROGRAM)$(X) '$(DESTDIR)$(bindir)' +endif # PROGRAM + +installcontrol: $(addsuffix .control, $(EXTENSION)) +ifneq (,$(EXTENSION)) + $(INSTALL_DATA) $< '$(DESTDIR)$(datadir)/extension/' +endif + +installdata: $(DATA) $(DATA_built) +ifneq (,$(DATA)$(DATA_built)) + $(INSTALL_DATA) $^ '$(DESTDIR)$(datadir)/$(datamoduledir)/' +endif + +installdatatsearch: $(DATA_TSEARCH) +ifneq (,$(DATA_TSEARCH)) + $(INSTALL_DATA) $^ '$(DESTDIR)$(datadir)/tsearch_data/' +endif + +installdocs: $(DOCS) ifdef DOCS ifdef docdir - $(INSTALL_DATA) $(addprefix $(srcdir)/, $(DOCS)) '$(DESTDIR)$(docdir)/$(docmoduledir)/' + $(INSTALL_DATA) $^ '$(DESTDIR)$(docdir)/$(docmoduledir)/' endif # docdir endif # DOCS -ifdef PROGRAM - $(INSTALL_PROGRAM) $(PROGRAM)$(X) '$(DESTDIR)$(bindir)' -endif # PROGRAM + +installscripts: $(SCRIPTS) $(SCRIPTS_built) ifdef SCRIPTS - $(INSTALL_SCRIPT) $(addprefix $(srcdir)/, $(SCRIPTS)) '$(DESTDIR)$(bindir)/' + $(INSTALL_SCRIPT) $^ '$(DESTDIR)$(bindir)/' endif # SCRIPTS -ifdef SCRIPTS_built - $(INSTALL_SCRIPT) $(SCRIPTS_built) '$(DESTDIR)$(bindir)/' -endif # SCRIPTS_built ifdef MODULE_big install: install-lib @@ -263,6 +282,7 @@ test_files_build := $(patsubst $(srcdir) all: $(test_files_build) $(test_files_build): $(abs_builddir)/%: $(srcdir)/% + $(MKDIR_P) $(dir $@) ln -s $< $@ endif # VPATH debian/postgresql-contrib-9.3.postinst0000644000000000000000000000026113334546526015155 0ustar #!/bin/sh set -e VERSION=9.3 . /usr/share/postgresql-common/maintscripts-functions if [ "$1" = configure ]; then configure_contrib_version $VERSION "$2" fi #DEBHELPER# debian/postgresql-client-9.3.postinst0000644000000000000000000000026013334546526014772 0ustar #!/bin/sh set -e VERSION=9.3 . /usr/share/postgresql-common/maintscripts-functions if [ "$1" = configure ]; then configure_client_version $VERSION "$2" fi #DEBHELPER# debian/postgresql-server-dev-9.3.install0000644000000000000000000000014413334546526015362 0ustar usr/include/postgresql/9.3/* usr/lib/postgresql/9.3/lib/pgxs/* usr/lib/postgresql/9.3/bin/pg_config debian/compat0000644000000000000000000000000213334546551010375 0ustar 7 debian/postgresql-plpython-9.3.install0000644000000000000000000000020513334546526015153 0ustar usr/lib/postgresql/9.3/lib/plpython2.so usr/share/postgresql/9.3/extension/plpythonu* usr/share/postgresql/9.3/extension/plpython2u* debian/postgresql-doc-9.3.dirs0000644000000000000000000000005313334546526013337 0ustar /usr/share/doc/postgresql-doc-9.3/tutorial debian/copyright0000644000000000000000000002556313334546551011145 0ustar Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: PostgreSQL Source: ftp://ftp.postgresql.org/pub/source/ Files: * Copyright: Portions Copyright (c) 1996-2003, The PostgreSQL Global Development Group Portions Copyright (c) 1994, The Regents of the University of California License: Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies. . IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. . THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS. Files: src/backend/regex/* Copyright: Copyright (c) 1998, 1999 Henry Spencer. All rights reserved. License: Development of this software was funded, in part, by Cray Research Inc., UUNET Communications Services Inc., Sun Microsystems Inc., and Scriptics Corporation, none of whom are responsible for the results. The author thanks all of them. . Redistribution and use in source and binary forms -- with or without modification -- are permitted for any purpose, provided that redistributions in source form retain this entire copyright notice and indicate the origin and nature of any modifications. . I'd appreciate being given credit for this package in the documentation of software which uses it, but that is not a requirement. . THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL HENRY SPENCER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Files: src/backend/regex/regc_locale.c Copyright: Copyright (c) 1998 by Scriptics Corporation. License: Tcl Files: src/backend/regex/re_syntax.n Copyright: Copyright (c) 1998 Sun Microsystems, Inc. Copyright (c) 1999 Scriptics Corporation License: Tcl Files: contrib/fuzzystrmatch/dmetaphone.c Copyright: Copyright 2000, Maurice Aubrey Copyright 2003, North Carolina State Highway Patrol License: This module is free software; you may redistribute it and/or modify it under the same terms as Perl itself. . All rights reserved. . Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies. . IN NO EVENT SHALL THE NORTH CAROLINA STATE HIGHWAY PATROL BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE NORTH CAROLINA STATE HIGHWAY PATROL HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. . THE NORTH CAROLINA STATE HIGHWAY PATROL SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE NORTH CAROLINA STATE HIGHWAY PATROL HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS. . The license of Perl is: . This program is free software; you can redistribute it and/or modify it under the terms of either: . a) the GNU General Public License as published by the Free Software Foundation; either version 1, or (at your option) any later version, or . b) the "Artistic License" which comes with Perl. . On Debian GNU/Linux systems, the complete text of the GNU General Public License version 1 can be found in `/usr/share/common-licenses/GPL-1' and the Artistic Licence in `/usr/share/common-licenses/Artistic'. Files: contrib/pageinspect/btreefuncs.c contrib/pgstattuple/pgstatindex.c Copyright: Copyright (c) 2006 Satoshi Nagayasu License: Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies. . IN NO EVENT SHALL THE AUTHOR BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. . THE AUTHOR SPECIFICALLY DISCLAIMS ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE AUTHOR HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS. Files: contrib/pgrowlocks/* Copyright: Copyright (c) 2005-2006 Tatsuo Ishii License: Same license text as contrib/pageinspect/btreefuncs.c Files: contrib/pgstattuple/pgstattuple.c Copyright: Copyright (c) 2001, 2002 Tatsuo Ishii License: Same license text as contrib/pageinspect/btreefuncs.c Files: contrib/pgcrypto/crypt-des.c contrib/pgcrypto/fortuna.* contrib/pgcrypto/mbuf.* contrib/pgcrypto/pgp* contrib/pgcrypto/internal.c contrib/pgcrypto/internal-sha2.c contrib/pgcrypto/openssl.c contrib/pgcrypto/pgcrypto.* contrib/pgcrypto/px* contrib/pgcrypto/random.c contrib/pgcrypto/sha2.* Copyright: Copyright (c) 1994 David Burren Copyright (c) 2001, 2005 Marko Kreen Copyright (c) 2000-2001, Aaron D. Gifford License: BSD-3-clause Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of the author nor the names of other contributors may be used to endorse or promote products derived from this software without specific prior written permission. . THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Files: src/bin/pg_dump/* Copyright: Portions Copyright (c) 2000, Philip Warner License: Rights are granted to use this software in any way so long as this notice is not removed. The author is not responsible for loss or damages that may result from its use. Files: src/backend/utils/mb/Unicode/*.txt Copyright: Copyright (C) 2001 earthian@tama.or.jp, All Rights Reserved. Copyright (C) 2001 I'O, All Rights Reserved. Copyright (C) 2006 Project X0213, All Rights Reserved. License: You can use, modify, distribute this table freely. License: Tcl This software is copyrighted by the Regents of the University of California, Sun Microsystems, Inc., Scriptics Corporation, ActiveState Corporation and other parties. The following terms apply to all files associated with the software unless explicitly disclaimed in individual files. . The authors hereby grant permission to use, copy, modify, distribute, and license this software and its documentation for any purpose, provided that existing copyright notices are retained in all copies and that this notice is included verbatim in any distributions. No written agreement, license, or royalty fee is required for any of the authorized uses. Modifications to this software may be copyrighted by their authors and need not follow the licensing terms described here, provided that the new terms are clearly indicated on the first page of each file where they apply. . IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. . THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS. . GOVERNMENT USE: If you are acquiring this software on behalf of the U.S. government, the Government shall have only "Restricted Rights" in the software and related documentation as defined in the Federal Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you are acquiring the software on behalf of the Department of Defense, the software shall be classified as "Commercial Computer Software" and the Government shall have only "Restricted Rights" as defined in Clause 252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the authors grant the U.S. Government and others acting in its behalf permission to use and distribute the software in accordance with the terms specified in this license. debian/pycompat0000644000000000000000000000000213334546526010750 0ustar 2 debian/postgresql-pltcl-9.3.install0000644000000000000000000000027113334546526014417 0ustar usr/lib/postgresql/9.3/lib/pltcl.so usr/lib/postgresql/9.3/bin/pltcl_* usr/share/postgresql/9.3/extension/pltcl* usr/share/postgresql/9.3/unknown.pltcl /usr/share/locale/*/*/pltcl-*.mo debian/postgresql-9.3.install0000644000000000000000000000323013334546526013301 0ustar usr/lib/postgresql/9.3/bin/initdb usr/lib/postgresql/9.3/bin/pg_controldata usr/lib/postgresql/9.3/bin/pg_ctl usr/lib/postgresql/9.3/bin/pg_resetxlog usr/lib/postgresql/9.3/bin/pg_upgrade usr/lib/postgresql/9.3/bin/pg_xlogdump usr/lib/postgresql/9.3/bin/postgres usr/lib/postgresql/9.3/bin/postmaster usr/lib/postgresql/9.3/lib/*_and_*.so usr/lib/postgresql/9.3/lib/euc2004_sjis2004.so usr/lib/postgresql/9.3/lib/libpqwalreceiver.so usr/lib/postgresql/9.3/lib/plpgsql.so usr/lib/postgresql/9.3/lib/dict_snowball.so usr/lib/postgresql/9.3/lib/pg_upgrade_support.so usr/lib/postgresql/9.3/lib/tsearch2.so usr/share/locale/*/LC_MESSAGES/initdb-9.3.mo usr/share/locale/*/LC_MESSAGES/pg_controldata-9.3.mo usr/share/locale/*/LC_MESSAGES/pg_ctl-9.3.mo usr/share/locale/*/LC_MESSAGES/pg_resetxlog-9.3.mo usr/share/locale/*/LC_MESSAGES/postgres-9.3.mo usr/share/locale/*/LC_MESSAGES/plpgsql-9.3.mo usr/share/locale/*/*/plpython-*.mo usr/share/postgresql/9.3/extension/plpgsql* usr/share/postgresql/9.3/man/man1/initdb.1.gz usr/share/postgresql/9.3/man/man1/pg_controldata.1.gz usr/share/postgresql/9.3/man/man1/pg_ctl.1.gz usr/share/postgresql/9.3/man/man1/pg_resetxlog.1.gz usr/share/postgresql/9.3/man/man1/pg_upgrade.1.gz usr/share/postgresql/9.3/man/man1/pg_xlogdump.1.gz usr/share/postgresql/9.3/man/man1/postgres.1.gz usr/share/postgresql/9.3/man/man1/postmaster.1.gz usr/share/postgresql/9.3/timezonesets/* usr/share/postgresql/9.3/tsearch_data usr/share/postgresql/9.3/*.sql usr/share/postgresql/9.3/*.conf.sample usr/share/postgresql/9.3/postgres.bki usr/share/postgresql/9.3/postgres.description usr/share/postgresql/9.3/postgres.shdescription usr/share/postgresql/9.3/sql_features.txt debian/source/0000755000000000000000000000000013334546526010501 5ustar debian/source/options0000644000000000000000000000014413334546526012116 0ustar extend-diff-ignore = src/test/regress/sql/.+\.sql extend-diff-ignore = \.bzr-builddeb/default\.conf debian/source/format0000644000000000000000000000001413334546526011707 0ustar 3.0 (quilt) debian/postgresql-contrib-9.3.prerm0000644000000000000000000000025113334546526014416 0ustar #!/bin/sh set -e #DEBHELPER# VERSION=9.3 if [ "$1" = remove ]; then . /usr/share/postgresql-common/maintscripts-functions remove_contrib_version $VERSION fi debian/libecpg-compat3.install0000644000000000000000000000003513334546551013536 0ustar usr/lib/libecpg_compat.so.3* debian/libpq5.symbols0000644000000000000000000000723713334546526012020 0ustar libpq.so.5 libpq5 #MINVER# PQbackendPID@Base 0 PQbinaryTuples@Base 0 PQcancel@Base 0 PQclear@Base 0 PQclientEncoding@Base 0 PQcmdStatus@Base 0 PQcmdTuples@Base 0 PQconndefaults@Base 0 PQconnectPoll@Base 0 PQconnectStart@Base 0 PQconnectStartParams@Base 9.0~ PQconnectdb@Base 0 PQconnectdbParams@Base 9.0~ PQconnectionNeedsPassword@Base 8.3~rc1-1~ PQconnectionUsedPassword@Base 8.3~ PQconninfo@Base 9.3~ PQconninfoFree@Base 0 PQconninfoParse@Base 8.4~ PQconsumeInput@Base 0 PQcopyResult@Base 8.4~ PQdb@Base 0 PQdescribePortal@Base 0 PQdescribePrepared@Base 0 PQdisplayTuples@Base 0 PQdsplen@Base 0 PQencryptPassword@Base 0 PQendcopy@Base 0 PQenv2encoding@Base 0 PQerrorMessage@Base 0 PQescapeBytea@Base 0 PQescapeByteaConn@Base 0 PQescapeIdentifier@Base 9.0~ PQescapeLiteral@Base 9.0~ PQescapeString@Base 0 PQescapeStringConn@Base 0 PQexec@Base 0 PQexecParams@Base 0 PQexecPrepared@Base 0 PQfformat@Base 0 PQfinish@Base 0 PQfireResultCreateEvents@Base 8.4~ PQflush@Base 0 PQfmod@Base 0 PQfn@Base 0 PQfname@Base 0 PQfnumber@Base 0 PQfreeCancel@Base 0 PQfreeNotify@Base 0 PQfreemem@Base 0 PQfsize@Base 0 PQftable@Base 0 PQftablecol@Base 0 PQftype@Base 0 PQgetCancel@Base 0 PQgetCopyData@Base 0 PQgetResult@Base 0 PQgetisnull@Base 0 PQgetlength@Base 0 PQgetline@Base 0 PQgetlineAsync@Base 0 PQgetssl@Base 0 PQgetvalue@Base 0 PQhost@Base 0 PQinitOpenSSL@Base 8.4~ PQinitSSL@Base 0 PQinstanceData@Base 8.4~ PQisBusy@Base 0 PQisnonblocking@Base 0 PQisthreadsafe@Base 0 PQlibVersion@Base 9.1~ PQmakeEmptyPGresult@Base 0 PQmblen@Base 0 PQnfields@Base 0 PQnotifies@Base 0 PQnparams@Base 0 PQntuples@Base 0 PQoidStatus@Base 0 PQoidValue@Base 0 PQoptions@Base 0 PQparameterStatus@Base 0 PQparamtype@Base 0 PQpass@Base 0 PQping@Base 9.1~ PQpingParams@Base 9.1~ PQport@Base 0 PQprepare@Base 0 PQprint@Base 0 PQprintTuples@Base 0 PQprotocolVersion@Base 0 PQputCopyData@Base 0 PQputCopyEnd@Base 0 PQputline@Base 0 PQputnbytes@Base 0 PQregisterEventProc@Base 8.4~ PQregisterThreadLock@Base 0 PQrequestCancel@Base 0 PQresStatus@Base 0 PQreset@Base 0 PQresetPoll@Base 0 PQresetStart@Base 0 PQresultAlloc@Base 8.4~ PQresultErrorField@Base 0 PQresultErrorMessage@Base 0 PQresultInstanceData@Base 8.4~ PQresultSetInstanceData@Base 8.4~ PQresultStatus@Base 0 PQsendDescribePortal@Base 0 PQsendDescribePrepared@Base 0 PQsendPrepare@Base 0 PQsendQuery@Base 0 PQsendQueryParams@Base 0 PQsendQueryPrepared@Base 0 PQserverVersion@Base 0 PQsetClientEncoding@Base 0 PQsetErrorVerbosity@Base 0 PQsetInstanceData@Base 8.4~ PQsetNoticeProcessor@Base 0 PQsetNoticeReceiver@Base 0 PQsetResultAttrs@Base 8.4~ PQsetSingleRowMode@Base 9.2~beta3 PQsetdbLogin@Base 0 PQsetnonblocking@Base 0 PQsetvalue@Base 8.4~ PQsocket@Base 0 PQstatus@Base 0 PQtrace@Base 0 PQtransactionStatus@Base 0 PQtty@Base 0 PQunescapeBytea@Base 0 PQuntrace@Base 0 PQuser@Base 0 appendBinaryPQExpBuffer@Base 0 appendPQExpBuffer@Base 0 appendPQExpBufferChar@Base 0 appendPQExpBufferStr@Base 0 createPQExpBuffer@Base 0 destroyPQExpBuffer@Base 0 enlargePQExpBuffer@Base 0 initPQExpBuffer@Base 0 lo_close@Base 0 lo_creat@Base 0 lo_create@Base 0 lo_export@Base 0 lo_import@Base 0 lo_import_with_oid@Base 8.4~ lo_lseek64@Base 9.3~ lo_lseek@Base 0 lo_open@Base 0 lo_read@Base 0 lo_tell64@Base 9.3~ lo_tell@Base 0 lo_truncate64@Base 9.3~ lo_truncate@Base 8.3~ lo_unlink@Base 0 lo_write@Base 0 pg_char_to_encoding@Base 0 pg_encoding_to_char@Base 0 pg_utf_mblen@Base 0 pg_valid_server_encoding@Base 0 pg_valid_server_encoding_id@Base 8.3~beta1-2~ pgresStatus@Base 0 pqsignal@Base 0 printfPQExpBuffer@Base 0 resetPQExpBuffer@Base 0 termPQExpBuffer@Base 0 debian/libpq5.install0000644000000000000000000000007513334546551011765 0ustar usr/lib/libpq.so.5* usr/share/locale/*/LC_MESSAGES/libpq*.mo debian/libecpg-dev.install0000644000000000000000000000102113334547710012740 0ustar usr/include/postgresql/ecpg*.h usr/include/postgresql/informix/* usr/include/postgresql/pgtypes*.h usr/include/postgresql/sql3types.h usr/include/postgresql/sqlca.h usr/include/postgresql/sqlda*.h usr/lib/pkgconfig/libecpg_compat.pc usr/lib/pkgconfig/libecpg.pc usr/lib/pkgconfig/libpgtypes.pc usr/lib/postgresql/9.3/bin/ecpg usr/bin usr/lib/libecpg.so usr/lib/libecpg_compat.so usr/lib/libpgtypes.so usr/lib/libecpg.a usr/lib/libecpg_compat.a usr/lib/libpgtypes.a usr/share/postgresql/9.3/man/man1/ecpg.1.gz /usr/share/man/man1 debian/postgresql-contrib-9.3.install0000644000000000000000000000471013334546526014743 0ustar usr/share/doc/postgresql-doc-9.3/extension/* usr/share/doc/postgresql-contrib-9.3 usr/share/postgresql/9.3/extension/* usr/lib/postgresql/9.3/lib/auth_delay.so usr/lib/postgresql/9.3/bin/pg_archivecleanup usr/lib/postgresql/9.3/bin/oid2name usr/lib/postgresql/9.3/bin/pgbench usr/lib/postgresql/9.3/bin/vacuumlo usr/lib/postgresql/9.3/bin/pg_standby usr/lib/postgresql/9.3/bin/pg_test_fsync usr/lib/postgresql/9.3/bin/pg_test_timing usr/lib/postgresql/9.3/lib/_int.so usr/lib/postgresql/9.3/lib/autoinc.so usr/lib/postgresql/9.3/lib/btree_gist.so usr/lib/postgresql/9.3/lib/chkpass.so usr/lib/postgresql/9.3/lib/cube.so usr/lib/postgresql/9.3/lib/dblink.so usr/lib/postgresql/9.3/lib/dummy_seclabel.so usr/lib/postgresql/9.3/lib/earthdistance.so usr/lib/postgresql/9.3/lib/file_fdw.so usr/lib/postgresql/9.3/lib/fuzzystrmatch.so usr/lib/postgresql/9.3/lib/insert_username.so usr/lib/postgresql/9.3/lib/lo.so usr/lib/postgresql/9.3/lib/ltree.so usr/lib/postgresql/9.3/lib/moddatetime.so usr/lib/postgresql/9.3/lib/pageinspect.so usr/lib/postgresql/9.3/lib/passwordcheck.so usr/lib/postgresql/9.3/lib/pg_trgm.so usr/lib/postgresql/9.3/lib/pgcrypto.so usr/lib/postgresql/9.3/lib/pgstattuple.so usr/lib/postgresql/9.3/lib/refint.so usr/lib/postgresql/9.3/lib/seg.so usr/lib/postgresql/9.3/lib/tablefunc.so usr/lib/postgresql/9.3/lib/tcn.so usr/lib/postgresql/9.3/lib/timetravel.so usr/lib/postgresql/9.3/lib/pgxml.so usr/lib/postgresql/9.3/lib/pg_buffercache.so usr/lib/postgresql/9.3/lib/adminpack.so usr/lib/postgresql/9.3/lib/sslinfo.so usr/lib/postgresql/9.3/lib/isn.so usr/lib/postgresql/9.3/lib/hstore.so usr/lib/postgresql/9.3/lib/pgrowlocks.so usr/lib/postgresql/9.3/lib/pg_freespacemap.so usr/lib/postgresql/9.3/lib/uuid-ossp.so usr/lib/postgresql/9.3/lib/test_parser.so usr/lib/postgresql/9.3/lib/dict_int.so usr/lib/postgresql/9.3/lib/dict_xsyn.so usr/lib/postgresql/9.3/lib/auto_explain.so usr/lib/postgresql/9.3/lib/pg_stat_statements.so usr/lib/postgresql/9.3/lib/citext.so usr/lib/postgresql/9.3/lib/btree_gin.so usr/lib/postgresql/9.3/lib/unaccent.so usr/lib/postgresql/9.3/lib/worker_spi.so usr/lib/postgresql/9.3/lib/postgres_fdw.so usr/share/postgresql/9.3/man/man1/oid2name.1.gz usr/share/postgresql/9.3/man/man1/pg_test_fsync.1.gz usr/share/postgresql/9.3/man/man1/pg_archivecleanup.1.gz usr/share/postgresql/9.3/man/man1/pg_test_timing.1.gz usr/share/postgresql/9.3/man/man1/pg_standby.1.gz usr/share/postgresql/9.3/man/man1/pgbench.1.gz usr/share/postgresql/9.3/man/man1/vacuumlo.1.gz debian/postgresql-9.3.postrm0000644000000000000000000000344613334546526013170 0ustar #!/bin/sh set -e #DEBHELPER# VERSION=9.3 clean_dir() { if [ -d "$1" ] && [ ! -L "$1" ]; then rmdir "$1" >/dev/null 2>/dev/null || true fi } drop_cluster() { # if we still have the postgresql-common package, use it to also shutdown # server, etc.; otherwise just remove the directories if [ -x /usr/bin/pg_dropcluster ]; then pg_dropcluster --stop-server $VERSION "$1" else # remove data directory PGDATALINK="/etc/postgresql/$VERSION/$1/pgdata" if [ -e "$PGDATALINK" ]; then rm -rf $(readlink -f "$PGDATALINK") "$PGDATALINK" else rm -rf "/var/lib/postgresql/$VERSION/$1/" fi # remove log file, including rotated ones LOGLINK="/etc/postgresql/$VERSION/$1/log" if [ -e "$LOGLINK" ]; then LOG=$(readlink -f "$LOGLINK") rm -f $LOG* "$LOGLINK" else rm -f /var/log/postgresql/postgresql-$VERSION-"$1".log* fi # remove conffiles for f in pg_hba.conf pg_ident.conf postgresql.conf start.conf environment pg_ctl.conf; do rm -f /etc/postgresql/$VERSION/"$1"/$f done clean_dir /etc/postgresql/$VERSION/"$1" fi } if [ "$1" = purge ]; then [ -d "/etc/postgresql/$VERSION" ] || exit 0 if [ "$(ls /etc/postgresql/$VERSION)" ]; then for c in /etc/postgresql/$VERSION/*; do [ -e "$c/postgresql.conf" ] || continue cluster=$(basename "$c") echo "Dropping cluster $cluster..." drop_cluster "$cluster" done fi clean_dir /etc/postgresql/$VERSION clean_dir /etc/postgresql clean_dir /var/lib/postgresql/$VERSION clean_dir /var/lib/postgresql clean_dir /var/log/postgresql/$VERSION clean_dir /var/log/postgresql fi debian/libpq-dev.install0000644000000000000000000000074413334546551012457 0ustar usr/include/postgresql/internal/* usr/include/postgresql/libpq-fe.h usr/include/postgresql/libpq-events.h usr/include/postgresql/libpq/libpq-fs.h usr/include/postgresql/pg_config*.h usr/include/postgresql/postgres_ext.h usr/lib/pkgconfig/libpq.pc usr/lib/libpgcommon.a usr/lib/libpgport.a usr/lib/libpq.a usr/lib/libpq.so usr/lib/postgresql/9.3/bin/pg_config usr/bin usr/share/locale/*/LC_MESSAGES/pg_config-9.3.mo usr/share/postgresql/9.3/man/man1/pg_config.1.gz /usr/share/man/man1 debian/postgresql-plperl-9.3.install0000644000000000000000000000016213334546526014576 0ustar usr/lib/postgresql/9.3/lib/plperl.so usr/share/postgresql/9.3/extension/plperl* /usr/share/locale/*/*/plperl-*.mo debian/postgresql-doc-9.3.doc-base0000644000000000000000000000077713334546526014070 0ustar Document: postgresql-9.3 Title: PostgreSQL 9.3 Documentation Author: The PostgreSQL Global Development Group Abstract: The documentation for the PostgreSQL database management system, version 9.3. PostgreSQL is a sophisticated Object-Relational DBMS, supporting almost all SQL constructs, including subselects, transactions, and user-defined types and functions. Section: Data Management Format: HTML Index: /usr/share/doc/postgresql-doc-9.3/html/index.html Files: /usr/share/doc/postgresql-doc-9.3/html/* debian/postgresql-9.3.preinst0000644000000000000000000000064013334546526013321 0ustar #!/bin/sh set -e # DB format changed between beta 1 and 2 if [ "$1" = "upgrade" ] || [ "$1" = "install" ] && \ dpkg --compare-versions "$2" lt-nl "9.3~beta2"; then if pg_lsclusters -h | grep -q '^9.3'; then echo "ERROR: The database format changed between beta 1 and 2. Please dump your 9.3 clusters first and remove them, before attempting to upgrade the package." >&2 exit 1 fi fi #DEBHELPER# exit 0 debian/postgresql-client-9.3.install0000644000000000000000000000314713334546526014564 0ustar usr/lib/postgresql/9.3/bin/clusterdb usr/lib/postgresql/9.3/bin/pg_dumpall usr/lib/postgresql/9.3/bin/pg_dump usr/lib/postgresql/9.3/bin/pg_basebackup usr/lib/postgresql/9.3/bin/pg_isready usr/lib/postgresql/9.3/bin/pg_receivexlog usr/lib/postgresql/9.3/bin/createdb usr/lib/postgresql/9.3/bin/createlang usr/lib/postgresql/9.3/bin/createuser usr/lib/postgresql/9.3/bin/dropdb usr/lib/postgresql/9.3/bin/droplang usr/lib/postgresql/9.3/bin/dropuser usr/lib/postgresql/9.3/bin/reindexdb usr/lib/postgresql/9.3/bin/pg_restore usr/lib/postgresql/9.3/bin/psql usr/lib/postgresql/9.3/bin/vacuumdb usr/share/postgresql/9.3/man/man1/pg_basebackup.1.gz usr/share/postgresql/9.3/man/man1/pg_isready.1.gz usr/share/postgresql/9.3/man/man1/pg_receivexlog.1.gz usr/share/postgresql/9.3/man/man1/pg_restore.1.gz usr/share/postgresql/9.3/man/man1/psql.1.gz usr/share/postgresql/9.3/man/man1/vacuumdb.1.gz usr/share/postgresql/9.3/man/man1/clusterdb.1.gz usr/share/postgresql/9.3/man/man1/pg_dump.1.gz usr/share/postgresql/9.3/man/man1/pg_dumpall.1.gz usr/share/postgresql/9.3/man/man1/createdb.1.gz usr/share/postgresql/9.3/man/man1/createlang.1.gz usr/share/postgresql/9.3/man/man1/createuser.1.gz usr/share/postgresql/9.3/man/man1/dropdb.1.gz usr/share/postgresql/9.3/man/man1/droplang.1.gz usr/share/postgresql/9.3/man/man1/dropuser.1.gz usr/share/postgresql/9.3/man/man1/reindexdb.1.gz usr/share/postgresql/9.3/man/man7/ usr/share/postgresql/9.3/psqlrc.sample usr/share/locale/*/LC_MESSAGES/pg_dump-9.3.mo usr/share/locale/*/LC_MESSAGES/psql-9.3.mo usr/share/locale/*/LC_MESSAGES/pgscripts-9.3.mo usr/share/locale/*/LC_MESSAGES/pg_basebackup-9.3.mo debian/libecpg6.symbols0000644000000000000000000000131113334546526012302 0ustar libecpg.so.6 libecpg6 #MINVER# ECPGallocate_desc@Base 0 ECPGconnect@Base 0 ECPGdeallocate@Base 0 ECPGdeallocate_all@Base 0 ECPGdeallocate_desc@Base 0 ECPGdebug@Base 0 ECPGdescribe@Base 0 ECPGdisconnect@Base 0 ECPGdo@Base 0 ECPGdo_descriptor@Base 0 ECPGfree_auto_mem@Base 0 ECPGget_PGconn@Base 8.3.1-2~ ECPGget_desc@Base 0 ECPGget_desc_header@Base 0 ECPGget_sqlca@Base 0 ECPGget_var@Base 9.0~ ECPGis_noind_null@Base 0 ECPGprepare@Base 0 ECPGprepared_statement@Base 0 ECPGset_desc@Base 0 ECPGset_desc_header@Base 0 ECPGset_noind_null@Base 0 ECPGset_var@Base 9.0~ ECPGsetcommit@Base 0 ECPGsetconn@Base 0 ECPGstatus@Base 0 ECPGtrans@Base 0 ECPGtransactionStatus@Base 9.0~ sqlprint@Base 0 debian/changelog0000644000000000000000000010553513335071115011050 0ustar postgresql-9.3 (9.3.24-0ubuntu0.14.04) trusty-security; urgency=medium * New upstream release (LP: #1786938) - Fix failure to reset libpq's state fully between connection attempts . An unprivileged user of dblink or postgres_fdw could bypass the checks intended to prevent use of server-side credentials, such as a ~/.pgpass file owned by the operating-system user running the server. Servers allowing peer authentication on local connections are particularly vulnerable. Other attacks such as SQL injection into a postgres_fdw session are also possible. Attacking postgres_fdw in this way requires the ability to create a foreign server object with selected connection parameters, but any user with access to dblink could exploit the problem. In general, an attacker with the ability to select the connection parameters for a libpq-using application could cause mischief, though other plausible attack scenarios are harder to think of. Our thanks to Andrew Krasichkov for reporting this issue. (CVE-2018-10915) - d/libecpg-dev.install: Add new pgtypes header. - d/libpgtypes3.symbols: Add new pgtypes symbol. - Details about these and other changes can be found at https://www.postgresql.org/docs/9.3/static/release-9-3-24.html -- Christian Ehrhardt Tue, 14 Aug 2018 14:49:12 +0200 postgresql-9.3 (9.3.23-0ubuntu0.14.04) trusty; urgency=medium * New upstream release (LP: #1769888) - A dump/restore is not required for those running 9.3.X. However, if the function marking mistakes mentioned in the first changelog entry affect you, you will want to take steps to correct your database catalogs. - Details about changes can be found at https://www.postgresql.org/docs/9.3/static/release-9-3-23.html -- Christian Ehrhardt Tue, 08 May 2018 15:17:51 +0200 postgresql-9.3 (9.3.22-0ubuntu0.14.04) trusty-security; urgency=medium * New upstream release (LP: #1752271) 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) - Details about other changes can be found at https://www.postgresql.org/docs/9.3/static/release-9-3-22.html -- Christian Ehrhardt Wed, 28 Feb 2018 09:59:05 +0100 postgresql-9.3 (9.3.21-0ubuntu0.14.04) trusty-security; urgency=medium * New upstream release (LP: #1747676) - Ensure that all temporary files made by pg_upgrade are non-world-readable (CVE-2018-1053) - Details about other changes at full changelog: https://www.postgresql.org/docs/9.3/static/release-9-3-21.html -- Christian Ehrhardt Tue, 06 Feb 2018 15:19:51 +0100 postgresql-9.3 (9.3.20-0ubuntu0.14.04) trusty-security; urgency=medium * New upstream release (LP: #1730661) - Details about other changes at full changelog: https://www.postgresql.org/docs/9.3/static/release-9-3-20.html -- Christian Ehrhardt Tue, 07 Nov 2017 14:33:47 +0100 postgresql-9.3 (9.3.19-0ubuntu0.14.04) trusty; urgency=medium * New upstream release (LP: #1713979) - fix upgrade regressions of the former security release - Details about other changes at full changelog: https://www.postgresql.org/docs/9.3/static/release-9-3-19.html -- Christian Ehrhardt Wed, 30 Aug 2017 13:00:40 +0200 postgresql-9.3 (9.3.18-0ubuntu0.14.04.1) trusty-security; urgency=medium * SECURITY UPDATE: Update to 9.3.18 to fix security issues - Further restrict visibility of pg_user_mappings.umoptions, to protect passwords stored as user mapping options (CVE-2017-7547) - Disallow empty passwords in all password-based authentication methods (CVE-2017-7546) - Make lo_put() check for UPDATE privilege on the target large object (CVE-2017-7548) -- Marc Deslauriers Mon, 14 Aug 2017 10:28:33 -0400 postgresql-9.3 (9.3.17-0ubuntu0.14.04) trusty; urgency=medium * New upstream release (LP: #1690730) - Restrict visibility of pg_user_mappings.umoptions, to protect passwords stored as user mapping options (CVE-2017-7486) - Prevent exposure of statistical information via leaky operators (CVE-2017-7484) - Restore libpq's recognition of the PGREQUIRESSL environment variable (CVE-2017-7485) - A dump/restore is not required for those running 9.3.X. - However, if you use foreign data servers that make use of user passwords for authentication, see the first changelog entry. - Details about other changes at full changelog: https://www.postgresql.org/docs/9.3/static/release-9-3-17.html -- Christian Ehrhardt Mon, 15 May 2017 08:45:01 +0200 postgresql-9.3 (9.3.16-0ubuntu0.14.04) trusty; urgency=medium * New upstream release (LP: #1664478) - Fix a race condition that could cause indexes built with CREATE INDEX CONCURRENTLY to be corrupt (Pavan Deolasee, Tom Lane). If CREATE INDEX CONCURRENTLY was used to build an index that depends on a column not previously indexed, then rows inserted or updated by transactions that ran concurrently with the CREATE INDEX command could have received incorrect index entries. If you suspect this may have happened, the most reliable solution is to rebuild affected indexes after installing this update - Details about other changes: https://www.postgresql.org/docs/9.3/static/release-9-3-16.html -- Christian Ehrhardt Tue, 14 Feb 2017 09:29:18 +0100 postgresql-9.3 (9.3.15-0ubuntu0.14.04) trusty-proposed; urgency=medium * New upstream bug fix release (LP: #1637236) - Fix WAL-logging of truncation of relation free space maps and visibility maps. It was possible for these files to not be correctly restored during crash recovery, or to be written incorrectly on a standby server. Bogus entries in a free space map could lead to attempts to access pages that have been truncated away from the relation itself, typically producing errors like "could not read block XXX: read only 0 of 8192 bytes". Checksum failures in the visibility map are also possible, if checksumming is enabled. Procedures for determining whether there is a problem and repairing it if so are discussed at https://wiki.postgresql.org/wiki/Free_Space_Map_Problems - Details about other changes: http://www.postgresql.org/docs/9.3/static/release-9-3-15.html -- Martin Pitt Thu, 27 Oct 2016 21:20:52 +0200 postgresql-9.3 (9.3.14-0ubuntu0.14.04) trusty-security; urgency=medium * New upstream security/bug fix release (LP: #1614113): - Fix possible mis-evaluation of nested CASE-WHEN expressions A CASE expression appearing within the test value subexpression of another CASE could become confused about whether its own test value was null or not. Also, inlining of a SQL function implementing the equality operator used by a CASE expression could result in passing the wrong test value to functions called within a CASE expression in the SQL function's body. If the test values were of different data types, a crash might result; moreover such situations could be abused to allow disclosure of portions of server memory. (CVE-2016-5423) - Fix client programs' handling of special characters in database and role names Numerous places in vacuumdb and other client programs could become confused by database and role names containing double quotes or backslashes. Tighten up quoting rules to make that safe. Also, ensure that when a conninfo string is used as a database name parameter to these programs, it is correctly treated as such throughout. Fix handling of paired double quotes in psql's \connect and \password commands to match the documentation. Introduce a new -reuse-previous option in psql's \connect command to allow explicit control of whether to re-use connection parameters from a previous connection. (Without this, the choice is based on whether the database name looks like a conninfo string, as before.) This allows secure handling of database names containing special characters in pg_dumpall scripts. pg_dumpall now refuses to deal with database and role names containing carriage returns or newlines, as it seems impractical to quote those characters safely on Windows. In future we may reject such names on the server side, but that step has not been taken yet. These are considered security fixes because crafted object names containing special characters could have been used to execute commands with superuser privileges the next time a superuser executes pg_dumpall or other routine maintenance operations. (CVE-2016-5424) - Details: http://www.postgresql.org/docs/9.3/static/release-9-3-14.html -- Martin Pitt Wed, 17 Aug 2016 16:37:41 +0200 postgresql-9.3 (9.3.13-0ubuntu0.14.04) trusty-proposed; urgency=medium * New upstream bug fix release. (LP: #1581016) - See http://www.postgresql.org/docs/9.3/static/release-9-3-13.html for details. -- Martin Pitt Thu, 12 May 2016 16:06:03 +0200 postgresql-9.3 (9.3.12-0ubuntu0.14.04) trusty-proposed; urgency=medium * New upstream bug fix release. (LP: #1564268) - See http://www.postgresql.org/about/news/1656/ for details. -- Martin Pitt Thu, 31 Mar 2016 11:04:53 +0200 postgresql-9.3 (9.3.11-0ubuntu0.14.04) trusty-security; urgency=medium * New upstream security/bug fix release: (LP: #1544576) - Fix infinite loops and buffer-overrun problems in regular expressions. Very large character ranges in bracket expressions could cause infinite loops in some cases, and memory overwrites in other cases. (CVE-2016-0773) - Prevent certain PL/Java parameters from being set by non-superusers. This change mitigates a PL/Java security bug (CVE-2016-0766), which was fixed in PL/Java by marking these parameters as superuser-only. To fix the security hazard for sites that update PostgreSQL more frequently than PL/Java, make the core code aware of them also. - See release notes for details about other fixes. -- Martin Pitt Thu, 11 Feb 2016 15:44:43 +0100 postgresql-9.3 (9.3.10-0ubuntu0.14.04) trusty-security; urgency=medium * New upstream security/bug fix release: (LP: #1504132) - Guard against stack overflows in json parsing. If an application constructs PostgreSQL json or jsonb values from arbitrary user input, the application's users can reliably crash the PostgreSQL server, causing momentary denial of service. (CVE-2015-5289) - Fix contrib/pgcrypto to detect and report too-short crypt() salts Certain invalid salt arguments crashed the server or disclosed a few bytes of server memory. We have not ruled out the viability of attacks that arrange for presence of confidential information in the disclosed bytes, but they seem unlikely. (CVE-2015-5288) - See release notes for details about other fixes. -- Martin Pitt Thu, 08 Oct 2015 15:42:16 +0200 postgresql-9.3 (9.3.9-0ubuntu0.14.04) trusty-proposed; urgency=medium * New upstream bug fix release (LP: #1464669) - Fix possible failure to recover from an inconsistent database state - Fix rare failure to invalidate relation cache init file - See http://www.postgresql.org/about/news/1592/ for details. -- Martin Pitt Fri, 12 Jun 2015 15:59:10 +0200 postgresql-9.3 (9.3.8-0ubuntu0.4.04) trusty-proposed; urgency=medium * New upstream bug fix release (LP: #1461425) - Avoid failures while fsync'ing data directory during crash restart. In the previous minor releases we added a patch to fsync everything in the data directory after a crash. Unfortunately its response to any error condition was to fail, thereby preventing the server from starting up, even when the problem was quite harmless. An example is that an unwritable file in the data directory would prevent restart on some platforms; but it is common to make SSL certificate files unwritable by the server. Revise this behavior so that permissions failures are ignored altogether, and other types of failures are logged but do not prevent continuing. - See release notes for details about other fixes. -- Martin Pitt Wed, 03 Jun 2015 09:54:24 +0200 postgresql-9.3 (9.3.7-0ubuntu0.14.04) trusty-security; urgency=medium * New upstream security/bug fix release (LP: #1457093) - Avoid possible crash when client disconnects just before the authentication timeout expires. If the timeout interrupt fired partway through the session shutdown sequence, SSL-related state would be freed twice, typically causing a crash and hence denial of service to other sessions. Experimentation shows that an unauthenticated remote attacker could trigger the bug somewhat consistently, hence treat as security issue. (CVE-2015-3165) - Improve detection of system-call failures Our replacement implementation of snprintf() failed to check for errors reported by the underlying system library calls; the main case that might be missed is out-of-memory situations. In the worst case this might lead to information exposure, due to our code assuming that a buffer had been overwritten when it hadn't been. Also, there were a few places in which security-relevant calls of other system library functions did not check for failure. It remains possible that some calls of the *printf() family of functions are vulnerable to information disclosure if an out-of-memory error occurs at just the wrong time. We judge the risk to not be large, but will continue analysis in this area. (CVE-2015-3166) - In contrib/pgcrypto, uniformly report decryption failures as Wrong key or corrupt data Previously, some cases of decryption with an incorrect key could report other error message texts. It has been shown that such variance in error reports can aid attackers in recovering keys from other systems. While it's unknown whether pgcrypto's specific behaviors are likewise exploitable, it seems better to avoid the risk by using a one-size-fits-all message. (CVE-2015-3167) - Protect against wraparound of multixact member IDs Under certain usage patterns, the existing defenses against this might be insufficient, allowing pg_multixact/members files to be removed too early, resulting in data loss. The fix for this includes modifying the server to fail transactions that would result in overwriting old multixact member ID data, and improving autovacuum to ensure it will act proactively to prevent multixact member ID wraparound, as it does for transaction ID wraparound. - See release notes for details about other fixes. -- Martin Pitt Wed, 20 May 2015 23:08:58 +0200 postgresql-9.3 (9.3.6-0ubuntu0.14.04) trusty-security; urgency=medium * New upstream security/bug fix release (LP: #1418928) - Fix buffer overruns in to_char() [CVE-2015-0241] - Fix buffer overruns in contrib/pgcrypto [CVE-2015-0243] - Fix possible loss of frontend/backend protocol synchronization after an error [CVE-2015-0244] - Fix information leak via constraint-violation error messages [CVE-2014-8161] - See release notes for details about other fixes: http://www.postgresql.org/about/news/1569/ -- Martin Pitt Fri, 06 Feb 2015 12:47:00 +0100 postgresql-9.3 (9.3.5-0ubuntu0.14.04.1) trusty-proposed; urgency=medium * New upstream bug fix release: (LP: #1348176) - pg_upgrade: Users who upgraded to version 9.3 using pg_upgrade may have an issue with transaction information which causes VACUUM to eventually fail. These users should run the script provided in the release notes to determine if their installation is affected, and then take the remedy steps outlined there. - Various data integrity and other bug fixes. - Secure Unix-domain sockets of temporary postmasters started during make check. Any local user able to access the socket file could connect as the server's bootstrap superuser, then proceed to execute arbitrary code as the operating-system user running the test, as we previously noted in CVE-2014-0067. This change defends against that risk by placing the server's socket in a temporary, mode 0700 subdirectory of /tmp. - See release notes for details: http://www.postgresql.org/about/news/1534/ * Remove pg_regress patches to support --host=/path, obsolete with above upstream changes and not applicable any more. * Drop tcl8.6 patch, applied upstream. * Add missing logrotate test dependency. -- Martin Pitt Thu, 24 Jul 2014 16:13:59 +0200 postgresql-9.3 (9.3.4-1) unstable; urgency=medium * New upstream bugfix release. Most notable change: Fix WAL replay of locking an already-updated tuple (Andres Freund, Álvaro Herrera) This error caused updated rows to not be found by index scans, resulting in inconsistent query results depending on whether an index scan was used. Subsequent processing could result in constraint violations, since the previously updated row would not be found by later index searches, thus possibly allowing conflicting rows to be inserted. Since this error is in WAL replay, it would only manifest during crash recovery or on standby servers. The improperly-replayed case most commonly arises when a table row that is referenced by a foreign-key constraint is updated concurrently with creation of a referencing row. * Compile with -fno-omit-frame-pointer on amd64 to facilitate hierarchical profile generation. (Closes: #730134) * Remove obsolete configure option --with-tkconfig. -- Christoph Berg Tue, 18 Mar 2014 07:19:37 +0100 postgresql-9.3 (9.3.3-2) unstable; urgency=medium [ Martin Pitt ] * Add missing build-essential test depends, for 180_ecpg.t. [ Christoph Berg ] * Don't install server includefiles in libpq-dev. (Closes: #314427) * Remove contrib/file_fdw/sql/file_fdw.sql on clean. -- Christoph Berg Wed, 12 Mar 2014 12:57:20 +0100 postgresql-9.3 (9.3.3-1) unstable; urgency=medium [ Christoph Berg ] * New upstream security/bugfix release. + Shore up GRANT ... WITH ADMIN OPTION restrictions (Noah Misch) Granting a role without ADMIN OPTION is supposed to prevent the grantee from adding or removing members from the granted role, but this restriction was easily bypassed by doing SET ROLE first. The security impact is mostly that a role member can revoke the access of others, contrary to the wishes of his grantor. Unapproved role member additions are a lesser concern, since an uncooperative role member could provide most of his rights to others anyway by creating views or SECURITY DEFINER functions. (CVE-2014-0060) + Prevent privilege escalation via manual calls to PL validator functions (Andres Freund) The primary role of PL validator functions is to be called implicitly during CREATE FUNCTION, but they are also normal SQL functions that a user can call explicitly. Calling a validator on a function actually written in some other language was not checked for and could be exploited for privilege-escalation purposes. The fix involves adding a call to a privilege-checking function in each validator function. Non-core procedural languages will also need to make this change to their own validator functions, if any. (CVE-2014-0061) + Avoid multiple name lookups during table and index DDL (Robert Haas, Andres Freund) If the name lookups come to different conclusions due to concurrent activity, we might perform some parts of the DDL on a different table than other parts. At least in the case of CREATE INDEX, this can be used to cause the permissions checks to be performed against a different table than the index creation, allowing for a privilege escalation attack. (CVE-2014-0062) + Prevent buffer overrun with long datetime strings (Noah Misch) The MAXDATELEN constant was too small for the longest possible value of type interval, allowing a buffer overrun in interval_out(). Although the datetime input functions were more careful about avoiding buffer overrun, the limit was short enough to cause them to reject some valid inputs, such as input containing a very long timezone name. The ecpg library contained these vulnerabilities along with some of its own. (CVE-2014-0063) + Prevent buffer overrun due to integer overflow in size calculations (Noah Misch, Heikki Linnakangas) Several functions, mostly type input functions, calculated an allocation size without checking for overflow. If overflow did occur, a too-small buffer would be allocated and then written past. (CVE-2014-0064) + Prevent overruns of fixed-size buffers (Peter Eisentraut, Jozef Mlich) Use strlcpy() and related functions to provide a clear guarantee that fixed-size buffers are not overrun. Unlike the preceding items, it is unclear whether these cases really represent live issues, since in most cases there appear to be previous constraints on the size of the input string. Nonetheless it seems prudent to silence all Coverity warnings of this type. (CVE-2014-0065) + Avoid crashing if crypt() returns NULL (Honza Horak, Bruce Momjian) There are relatively few scenarios in which crypt() could return NULL, but contrib/chkpass would crash if it did. One practical case in which this could be an issue is if libc is configured to refuse to execute unapproved hashing algorithms (e.g., "FIPS mode"). (CVE-2014-0066) + Document risks of make check in the regression testing instructions (Noah Misch, Tom Lane) Since the temporary server started by make check uses "trust" authentication, another user on the same machine could connect to it as database superuser, and then potentially exploit the privileges of the operating-system user who started the tests. A future release will probably incorporate changes in the testing procedure to prevent this risk, but some public discussion is needed first. So for the moment, just warn people against using make check when there are untrusted users on the same machine. (CVE-2014-0067) + Rework tuple freezing protocol (Álvaro Herrera, Andres Freund) The logic for tuple freezing was unable to handle some cases involving freezing of multixact IDs, with the practical effect that shared row-level locks might be forgotten once old enough. Fixing this required changing the WAL record format for tuple freezing. While this is no issue for standalone servers, when using replication it means that standby servers must be upgraded to 9.3.3 or later before their masters are. An older standby will be unable to interpret freeze records generated by a newer master, and will fail with a PANIC message. (In such a case, upgrading the standby should be sufficient to let it resume execution.) * The upstream tarballs no longer contain a plain HISTORY file, but point to the html documentation. Note the location of these files in our changelog.gz file. * Teach configure to find tclsh8.6 where tclsh is not available. [ Martin Pitt ] * Build with LINUX_OOM_SCORE_ADJ=0 instead of the older LINUX_OOM_ADJ=0. All relevant distro releases (>= squeeze/lucid) use kernels which support /proc/pid/oom_score_adj, so avoid the dmesg warnings. (Closes: #646245, LP: #991725) * Bump Standards-Version to 3.9.5 (no changes necessary). * Build with tcl8.6 where available (>= Jessie, >= trusty). -- Christoph Berg Wed, 19 Feb 2014 10:15:39 +0100 postgresql-9.3 (9.3.2-1) unstable; urgency=low [ Martin Pitt ] * Add 03-config-update.patch: Refresh config.{guess,sub} to latest version for enabling ports, in particular the upcoming ppc64el. [ Christoph Berg ] * New upstream bugfix release. + Fix "VACUUM"'s tests to see whether it can update relfrozenxid (Andres Freund) In some cases "VACUUM" (either manual or autovacuum) could incorrectly advance a table's relfrozenxid value, allowing tuples to escape freezing, causing those rows to become invisible once 2^31 transactions have elapsed. The probability of data loss is fairly low since multiple incorrect advancements would need to happen before actual loss occurs, but it's not zero. In 9.2.0 and later, the probability of loss is higher, and it's also possible to get "could not access status of transaction" errors as a consequence of this bug. Users upgrading from releases 9.0.4 or 8.4.8 or earlier are not affected, but all later versions contain the bug. The issue can be ameliorated by, after upgrading, vacuuming all tables in all databases while having vacuum_freeze_table_age set to zero. This will fix any latent corruption but will not be able to fix all pre-existing data errors. However, an installation can be presumed safe after performing this vacuuming if it has executed fewer than 2^31 update transactions in its lifetime (check this with SELECT txid_current() < 2^31). + Fix multiple bugs in MultiXactId freezing (Andres Freund, Alvaro Herrera) These bugs could lead to "could not access status of transaction" errors, or to duplicate or vanishing rows. Users upgrading from releases prior to 9.3.0 are not affected. The issue can be ameliorated by, after upgrading, vacuuming all tables in all databases while having vacuum_freeze_table_age set to zero. This will fix latent corruption but will not be able to fix all pre-existing data errors. As a separate issue, these bugs can also cause standby servers to get out of sync with the primary, thus exhibiting data errors that are not in the primary. Therefore, it's recommended that 9.3.0 and 9.3.1 standby servers be re-cloned from the primary (e.g., with a new base backup) after upgrading. + Fix initialization of "pg_clog" and "pg_subtrans" during hot standby startup (Andres Freund, Heikki Linnakangas) This bug can cause data loss on standby servers at the moment they start to accept hot-standby queries, by marking committed transactions as uncommitted. The likelihood of such corruption is small unless, at the time of standby startup, the primary server has executed many updating transactions since its last checkpoint. Symptoms include missing rows, rows that should have been deleted being still visible, and obsolete versions of updated rows being still visible alongside their newer versions. This bug was introduced in versions 9.3.0, 9.2.5, 9.1.10, and 9.0.14. Standby servers that have only been running earlier releases are not at risk. It's recommended that standby servers that have ever run any of the buggy releases be re-cloned from the primary (e.g., with a new base backup) after upgrading. * Refresh debian/patches/62-pg_upgrade-test-in-tmp. -- Christoph Berg Tue, 03 Dec 2013 09:18:41 +0100 postgresql-9.3 (9.3.1-1) unstable; urgency=low * New upstream release. - Update hstore extension with JSON functionality Users who installed hstore prior to 9.3.1 must execute: ALTER EXTENSION hstore UPDATE; to add two new JSON functions and a cast. - Some bug fixes, see HISTORY for details. -- Martin Pitt Tue, 08 Oct 2013 10:54:46 +0200 postgresql-9.3 (9.3.0-2) unstable; urgency=low [ Martin Pitt ] * Drop the "beta" warning from package description, this is the final version now. -- Christoph Berg Tue, 10 Sep 2013 09:34:39 +0200 postgresql-9.3 (9.3.0-1) unstable; urgency=low * New upstream release. * pgxs.mk: Make the install targets depend on installdirs. -- Christoph Berg Wed, 04 Sep 2013 18:53:05 +0200 postgresql-9.3 (9.3~rc1-2) unstable; urgency=low * Rebuild against Perl 5.18. -- Martin Pitt Tue, 27 Aug 2013 11:27:10 +0200 postgresql-9.3 (9.3~rc1-1) unstable; urgency=low [ Martin Pitt ] * New upstream release: first 9.3 release candidate. - Add locking around SSL_context usage in libpq, to make it thread safe. (Closes: #718460) * First upload to unstable, 9.3 final will be released soon and now is the time for testing and porting extensions. * debian/rules: Support multi-arch locations of {tcl,tk}-config. * debian/rules: Don't build with kerberos and LDAP support for DEB_STAGE=stage1 to aid with bootstrapping. * debian/tests/control: Add missing net-tools dependency (for ifconfig). * debian/rules: Call dh with --parallel. * debian/control: Explicitly Conflicts/Replaces postgresql-9.1-dbg, as that did not yet have a "Provides: postgresql-dbg". (Closes: #717982) [ Christoph Berg ] * Pull 6697aa2bc25c83b88d6165340348a31328c35de6 and 82b0102650cf85268145a46f0ab488bacf6599a1 from upstream head to better support VPATH builds of PGXS modules. * debian/rules: Call make check-world without -k and use a random port number for pg_regress. -- Martin Pitt Thu, 22 Aug 2013 10:19:13 +0200 postgresql-9.3 (9.3~beta2-2) experimental; urgency=low * debian/postgresql-9.3.preinst: Abort upgrade if there are still clusters with the 9.3beta1 format, these need to be dumped/dropped first. (Closes: #714328) -- Martin Pitt Fri, 28 Jun 2013 14:37:06 +0200 postgresql-9.3 (9.3~beta2-1) experimental; urgency=low [ Christoph Berg ] * hurd-i386: Ignore testsuite failures so we have a working libpq5 (they don't implement semaphores so the server won't even start). * Mark postgresql-9.3 as beta in the description, suggested by Joshua D. Drake. [ Martin Pitt ] * New upstream release 9.3 beta2. -- Martin Pitt Wed, 26 Jun 2013 15:13:32 +0200 postgresql-9.3 (9.3~beta1-3) experimental; urgency=low * sparc, alpha: Remove -O1 - we have been using this since 2007, but now it looks the other way round, "make check" fails on sparc with -O1, but works with -O2. * kfreebsd-*: Ignore testsuite failures until we resolve the plperl failures, see #704802. -- Christoph Berg Fri, 31 May 2013 16:34:34 -0700 postgresql-9.3 (9.3~beta1-2) experimental; urgency=low * Update watch file for 9.3. * 64-pg_upgrade-sockdir: If cwd is too long to use as socketdir in pg_upgrade, fall back to /tmp. (A Unix socket path must not be longer than 107 chars.) -- Christoph Berg Mon, 13 May 2013 23:09:44 -0700 postgresql-9.3 (9.3~beta1-1) experimental; urgency=low [ Christoph Berg ] * Update for 9.3. Packaging based on 9.2 branch. * Remove 03-python-includedirs.patch, implemented upstream. * libpq5.symbols: Add new symbols: PQconninfo, lo_lseek64, lo_tell64, lo_truncate64. * debian/rules: Remove the temporary patches from pg_regress, and teach pg_regress to support unix socket dirs in --host. * debian/rules: Use "make check-world" to run the regression tests. Thanks to Peter Eisentraut for the suggestion. * 50-per-version-dirs.patch: Use @MAJORVERSION@ instead of a fixed version. * 61-extra_regress_opts: Add EXTRA_REGRESS_OPTS in Makefile.global(.in). * 62-pg_upgrade-test-in-tmp: Hardcode /tmp in pg_upgrade's test.sh. * 63-pg_upgrade-test-bindir: Pass PSQLDIR to the pg_regress call. * postgresql-9.3.install: Add pg_xlogdump. * postgresql-client-9.3.install: Add pg_isready. * libpq-dev.install: Add usr/lib/libpgcommon.a. * libpq-dev.install, libecpg-dev.install: Add pkgconfig files. * postgresql-contrib-9.3.install: Add usr/lib/postgresql/9.3/lib/postgres_fdw.so. [ Martin Pitt ] * Bump p-common dependency to >= 142, to ensure compatibility with 9.3, particularly for upgrades. -- Martin Pitt Wed, 08 May 2013 05:39:52 +0200 debian/libecpg-compat3.symbols0000644000000000000000000000143013334546526013562 0ustar libecpg_compat.so.3 libecpg-compat3 #MINVER# ECPG_informix_get_var@Base 0 ECPG_informix_reset_sqlca@Base 9.0~ ECPG_informix_set_var@Base 0 byleng@Base 0 decadd@Base 0 deccmp@Base 0 deccopy@Base 0 deccvasc@Base 0 deccvdbl@Base 0 deccvint@Base 0 deccvlong@Base 0 decdiv@Base 0 decmul@Base 0 decsub@Base 0 dectoasc@Base 0 dectodbl@Base 0 dectoint@Base 0 dectolong@Base 0 dtcurrent@Base 0 dtcvasc@Base 0 dtcvfmtasc@Base 0 dtsub@Base 0 dttoasc@Base 0 dttofmtasc@Base 0 intoasc@Base 0 ldchar@Base 0 rdatestr@Base 0 rdayofweek@Base 0 rdefmtdate@Base 0 rfmtdate@Base 0 rfmtlong@Base 0 rgetmsg@Base 0 risnull@Base 0 rjulmdy@Base 0 rmdyjul@Base 0 rsetnull@Base 0 rstrdate@Base 0 rtoday@Base 0 rtypalign@Base 0 rtypmsize@Base 0 rtypwidth@Base 0 rupshift@Base 0