Commit graph

50 commits

Author SHA1 Message Date
adam
6c545580f8 postgresql12: added version 12.0
Release 12:

General performance improvements, including:
* Optimizations to space utilization and read/write performance for B-tree indexes
* Partitioning performance enhancements, including improved query performance on tables with thousands of partitions, improved insertion performance with INSERT and COPY, and the ability to execute ALTER TABLE ATTACH PARTITION without blocking queries
* Automatic (but overridable) inlining of common table expressions (CTEs)
* Reduction of WAL overhead for creation of GiST, GIN, and SP-GiST indexes
* Support for covering GiST indexes, via the INCLUDE clause
* Multi-column most-common-value (MCV) statistics can be defined via CREATE STATISTICS, to support better plans for queries that test several non-uniformly-distributed columns

Enhancements to administrative functionality, including:
* REINDEX CONCURRENTLY can rebuild an index without blocking writes to its table
* pg_checksums can enable/disable page checksums (used for detecting data corruption) in an offline cluster
* Progress reporting statistics for CREATE INDEX, REINDEX, CLUSTER, VACUUM FULL, and pg_checksums

Support for the SQL/JSON path language

Stored generated columns

Nondeterministic ICU collations, enabling case-insensitive and accent-insensitive grouping and ordering

New authentication features, including:
* Encryption of TCP/IP connections when using GSSAPI authentication
* Discovery of LDAP servers using DNS SRV records
* Multi-factor authentication, using the clientcert=verify-full option combined with an additional authentication method in pg_hba.conf
2019-10-07 19:21:48 +00:00
adam
0bc15a6e5c Remove references to Postgresql 9.3 2019-05-21 05:52:31 +00:00
adam
eee51a9821 postgresql11: added version 11.0
PostgreSQL 11 provides users with improvements to overall performance of the database system, with specific enhancements associated with very large databases and high computational workloads. Further, PostgreSQL 11 makes significant improvements to the table partitioning system, adds support for stored procedures capable of transaction management, improves query parallelism and adds parallelized data definition capabilities, and introduces just-in-time (JIT) compilation for accelerating the execution of expressions in queries.
2018-10-23 16:02:51 +00:00
adam
8276c64ad4 Removed postgresql92 support 2018-05-21 08:07:49 +00:00
adam
f58d525a43 Added support for PostgreSQL 10.0 2017-10-23 20:34:27 +00:00
jlam
000f312c98 Use public SHLIB_TYPE instead of private _OPSYS_SHLIB_TYPE. 2017-06-01 13:30:24 +00:00
adam
f7716a4492 Removed databases/postgresql91 2017-05-24 19:51:12 +00:00
adam
8889df1526 Added postgresql96 support 2016-10-30 08:57:12 +00:00
wiz
fdee5ecd22 Bump pgsql default to 95. 2016-10-09 21:08:18 +00:00
tnn
307ed51e86 PostgreSQL 9.5 awareness 2016-02-25 21:39:07 +00:00
joerg
35841dc13b Unhook further PG 8.4 and 9.0 redirection. 2015-10-24 21:21:26 +00:00
joerg
b7008c73ea Drop EOLed PostgreSQL 8.4 and 9.0 from the supported list of PG
versions.
2015-10-24 21:18:12 +00:00
adam
e9d63c048f PostgreSQL 9.4.0:
This release adds many new features which enhance PostgreSQL's flexibility, scalability and performance for many different types of database users, including improvements to JSON support, replication and index performance.
2015-01-14 21:01:18 +00:00
joerg
a8dd640f08 Bump PostgreSQL default version to 9.3. 2014-06-10 14:21:37 +00:00
adam
f4dd376ce6 Added databases/postgresql93 version 9.3.0 2013-09-10 15:35:30 +00:00
adam
ea28815591 The PostgreSQL Global Development Group has released a security update to all current versions of the PostgreSQL database system, including versions 9.2.4, 9.1.9, 9.0.13, and 8.4.17. This update fixes a high-exposure security vulnerability in versions 9.0 and later. All users of the affected versions are strongly urged to apply the update immediately.
A major security issue fixed in this release, CVE-2013-1899, makes it possible for a connection request containing a database name that begins with "-" to be crafted that can damage or destroy files within a server's data directory. Anyone with access to the port the PostgreSQL server listens on can initiate this request.

Two lesser security fixes are also included in this release: CVE-2013-1900, wherein random numbers generated by contrib/pgcrypto functions may be easy for another database user to guess, and CVE-2013-1901, which mistakenly allows an unprivileged user to run commands that could interfere with in-progress backups. Finally, this release fixes two security issues with the graphical installers for Linux and Mac OS X: insecure passing of superuser passwords to a script, CVE-2013-1903 and the use of predictable filenames in /tmp CVE-2013-1902.
2013-04-04 21:08:25 +00:00
adam
98a0fe959f Added databases/postgresql92 version 9.2.1 2012-10-05 21:09:02 +00:00
asau
cab432b8e9 Default to PostgreSQL 9.1 as announced on pkgsrc-users and tech-pkg two weeks ago. 2012-08-02 03:53:19 +00:00
adam
1d2335aa54 Added databases/postgresql91 version 9.1.0 2011-09-15 08:35:40 +00:00
adam
0403ae2e0c Adjust installed version auto-detection 2011-05-08 19:29:02 +00:00
joerg
c8a8fd2d9b Remove PostgreSQL 8.2 from the list. 2010-10-12 16:44:19 +00:00
adam
1fa8fb1365 Added databases/postgresql90 version 9.0.0 2010-09-21 07:56:11 +00:00
joerg
ece478d819 Change PostgreSQL default to 8.4. 2010-02-10 19:33:54 +00:00
joerg
162524bc85 Unsupport PostgreSQL 8.1. Garbage collect detection of ancient versions. 2009-08-14 19:40:48 +00:00
adam
f21fbf16b8 Added databases/postgresql84 2009-07-29 06:33:03 +00:00
joerg
2a7055907f Make PostgreSQL 8.2 the default version. Bump all packages using it.
Remove PostgreSQL 8.0 as choice.
2008-03-13 17:38:48 +00:00
adam
2f7d2aaf29 Added postgresql83 2008-03-04 12:50:25 +00:00
rillig
6dd36d59da Added _VARGROUPS. 2007-06-06 12:40:05 +00:00
rillig
f6a8043bf5 Replaced the deprecated PKG_SKIP_REASON with PKG_FAIL_REASON. 2007-02-10 08:59:07 +00:00
joerg
331e2615fa Change PostgreSQL default version to 8.1 and bump revision of all
packages which have it active by default.
2006-12-28 12:12:57 +00:00
joerg
677b9da699 As discussed on tech-pkg, remove PostgreSQL 7.4. 2006-12-27 15:57:36 +00:00
adam
f3f2e225dc Support 8.1 and 8.2 for Darwin 2006-12-26 18:42:44 +00:00
adam
b74bfb9e0f Added postgresql82 version 8.2.0 2006-12-09 16:18:40 +00:00
rillig
6c8f1ff9e4 Added a stub describing the public interface of this file. 2006-10-18 20:48:58 +00:00
joerg
ebe30855cf One more reminder of PostgreSQL 7.3 to remove... 2006-06-06 19:43:43 +00:00
uebayasi
b79cc5ce5a postgresql81 has moved from wip to pkgsrc. 2006-03-20 14:48:45 +00:00
abs
f97bfe9e95 permit postgresl81 2006-01-08 12:53:53 +00:00
joerg
0b8b660c32 Change default PostgreSQL version to 8.0. 2005-11-11 15:47:52 +00:00
abs
dc52980e11 At least on NetBSD 2.0 i386 postgres80 is currently installing
lib/libecpg.so.5.0.0 not lib/libecpg.so.5.0
2005-08-06 23:01:19 +00:00
rillig
f5fcc97bca Added a variable PGSQL_VERSION that identifies the PostgreSQL version used. 2005-05-24 10:01:25 +00:00
jlam
564a72cde1 postgresql80-client is the correct BUILDLINK_PACKAGE word to use when
referring to BUILDLINK_* variables.
2005-05-12 22:19:16 +00:00
recht
e346f21641 catch up with PostgreSQL 8.0.2 and support Darwin .dylib 2005-04-11 20:35:24 +00:00
tv
fe3c1321bf USE_BUILDLINK3 is no longer optional (and cannot be turned off). Per mail
to tech-pkg:

=====

* USE_BUILDLINK3=YES will be unconditional.  (In fact, USE_BUILDLINK3 will
  be ignored altogether by mk/; but see below.)

* NO_BUILDLINK and NO_WRAPPER will be ignored by mk/.  If a build happens,
  these phases will happen.

* The existing NO_BUILD will imply the previous NO_BUILDLINK and NO_WRAPPER.
  If no build happens, those phases are not needed.

* NO_TOOLS will be ignored by mk/.  The tools phase, which provides much
  more than just the C compiler, will always happen regardless of package.
  This will make metapackage builds only slightly slower, in trade for far
  less user error.
2005-03-24 17:46:00 +00:00
jlam
da54b6a39a Set PGSQL_TYPE to the PKGBASE of the PostgreSQL library package that's
ultimately selected.  PGSQL_TYPE may be used to reference various
BUILDLINK_*.${PGSQL_TYPE} variables.
2005-03-17 21:44:58 +00:00
dan
690664a68f pg80 is now in databases, not wip 2005-02-07 04:12:49 +00:00
dan
3d6fb6d7cf don't recognise pg80 as pg74 also 2005-02-07 04:07:13 +00:00
abs
6a63f7037d allow postgresql80 (from wip), similar to java-vm.mk and jdk14 2005-02-01 11:07:31 +00:00
xtraeme
f20f07a4bf Add missing PKG_SKIP_REASON when ${_PGSQL_VERSION} is defined, but
the package is not postgresql "74" or "73".
2004-10-26 21:39:33 +00:00
recht
f8d7e38602 Export the according BUILDLINK_PREFIX of postgresql-lib as PGSQL_PREFIX. 2004-07-24 10:40:15 +00:00
recht
9416178d77 pgsql.buildlink3.mk is used to select a PostgreSQL version for use by
pkgsrc. It is modeled after lang/python/pyversion.mk and like it
could be influenced by user- and package-settable variables.

More precisely, tt's behaviour is controlled by the following
two variables:

- PGSQL_VERSION_DEFAULT
  A user-settable variable to choose the default PostgreSQL version.
  Default: 74

- PGSQL_VERSIONS_ACCEPTED
  A package-settable list of PostgreSQL versions accepted by the package.
  Default: 74 73

After postgresql-* has been reimported as postgresql73* all depending
packages should be changed to use mk/pgsql.buildlink3.mk.
2004-07-23 21:40:00 +00:00