1997-04-10 21:15:12 +02:00
# New ports collection makefile for: PostgreSQL
1998-11-22 22:33:20 +01:00
# Date created: November 13, 1998
1999-08-31 08:53:31 +02:00
# Whom: Marc G. Fournier <scrappy@FreeBSD.org>
1997-04-09 17:30:55 +02:00
#
1999-08-25 07:28:01 +02:00
# $FreeBSD$
1998-04-22 10:28:07 +02:00
#
1998-04-21 23:52:10 +02:00
2003-12-04 16:24:57 +01:00
PORTNAME ?= postgresql
2009-03-18 16:13:39 +01:00
PORTVERSION ?= 8.2.13
2002-02-19 09:23:22 +01:00
CATEGORIES ?= databases
2003-06-11 11:23:15 +02:00
MASTER_SITES = ${ MASTER_SITE_PGSQL }
2005-01-31 15:56:24 +01:00
MASTER_SITE_SUBDIR = source/v${ PORTVERSION }
2006-12-06 17:50:34 +01:00
PKGNAMESUFFIX ?= -server
2008-01-07 14:51:57 +01:00
DISTFILES ?= postgresql-${ PORTVERSION } ${ EXTRACT_SUFX }
1997-10-03 16:13:36 +02:00
2004-12-06 04:59:56 +01:00
MAINTAINER ?= girgen@FreeBSD.org
2003-10-13 11:54:16 +02:00
COMMENT ?= The most advanced open-source database available anywhere
1997-04-10 21:15:12 +02:00
2006-12-06 17:50:34 +01:00
CONFLICTS ?= ${ PORTNAME } -client-7.* \
${ PORTNAME } ${ PKGNAMESUFFIX } -7.* \
${ PORTNAME } -client-8.[ 0-13-9] * \
${ PORTNAME } ${ PKGNAMESUFFIX } -8.[ 0-13-9] *
2004-11-23 20:15:12 +01:00
2002-02-19 09:23:22 +01:00
WRKSRC = ${ WRKDIR } /postgresql-${ PORTVERSION }
2001-04-21 13:34:34 +02:00
DIST_SUBDIR = postgresql
2000-12-11 04:22:07 +01:00
2006-12-06 17:50:34 +01:00
UNIQUENAME ?= ${ PORTNAME } 82
2005-02-19 13:07:46 +01:00
LATEST_LINK ?= ${ PKGNAMEPREFIX } ${ UNIQUENAME } ${ PKGNAMESUFFIX }
2004-11-23 20:15:12 +01:00
PKGINSTALL ?= ${ PKGDIR } /pkg-install${ PKGNAMESUFFIX }
2003-12-04 13:00:49 +01:00
USE_BZIP2 = YES
2002-02-19 09:23:22 +01:00
USE_GMAKE = YES
GNU_CONFIGURE = YES
2004-11-23 20:15:12 +01:00
. i f d e f i n e d ( N O _ B U I L D )
. u n d e f U S E _ G M A K E
. u n d e f G N U _ C O N F I G U R E
. e n d i f
1997-10-05 00:43:26 +02:00
2005-01-31 01:36:16 +01:00
CONFIGURE_ARGS += --with-libraries= ${ LOCALBASE } /lib \
--with-includes= ${ LOCALBASE } /include \
2008-03-18 23:27:20 +01:00
--enable-thread-safety \
2005-01-31 01:36:16 +01:00
--with-docdir= ${ DOCSDIR }
2007-03-18 17:23:18 +01:00
CONFIGURE_ENV += LDFLAGS = " ${ LDFLAGS } " \
PTHREAD_CFLAGS = " ${ PTHREAD_CFLAGS } " \
PTHREAD_LIBS = " ${ PTHREAD_LIBS } "
2002-02-19 09:23:22 +01:00
2008-03-18 23:27:20 +01:00
CFLAGS += ${ PTHREAD_CFLAGS }
LDFLAGS += ${ PTHREAD_LIBS }
2004-11-23 20:15:12 +01:00
PLIST = ${ PKGDIR } /pkg-plist${ PKGNAMESUFFIX }
1997-10-05 00:43:26 +02:00
2005-05-11 02:40:15 +02:00
BUILD_DIRS ?= src/port src/timezone src/backend src/backend/utils/mb/conversion_procs \
2007-01-09 17:29:35 +01:00
src/bin/initdb src/bin/ipcclean src/bin/pg_ctl src/bin/pg_controldata \
src/bin/pg_resetxlog src/pl
2006-12-06 17:50:34 +01:00
2004-11-23 20:15:12 +01:00
INSTALL_DIRS ?= ${ BUILD_DIRS }
2002-02-19 09:23:22 +01:00
2004-11-23 20:15:12 +01:00
. i f ! d e f i n e d ( C L I E N T _ O N L Y ) & & ! d e f i n e d ( S L A V E _ O N L Y )
SERVER_ONLY = yes
2006-12-06 17:50:34 +01:00
USE_RC_SUBR = postgresql
SUB_FILES += dot.cshrc dot.profile
2004-11-23 20:15:12 +01:00
USE_PGSQL = yes
WANT_PGSQL_VER = ${ PORTVERSION : C /([0-9][0-9]*) \. ([0-9][0-9]*).*/ \1 \2 /g }
2003-12-04 13:00:49 +01:00
. e n d i f
2004-11-23 20:15:12 +01:00
. i f ! d e f i n e d ( S L A V E _ O N L Y )
OPTIONS = NLS "Use internationalized messages" on
2005-01-31 01:36:16 +01:00
. e n d i f
# Cannot check this with standard OPTION due to a catch-22.
# USE_OPENSSL must precede bsd.port.pre.mk, but then we don't know
# what OPTIONS are set.
#
# If you *don't* want SSL, set WITHOUT_SSL=YES when making
. i f ! d e f i n e d ( W I T H O U T _ S S L )
USE_OPENSSL = yes
CONFIGURE_ARGS += --with-openssl
2001-04-21 13:34:34 +02:00
. e n d i f
2004-11-23 20:15:12 +01:00
. i n c l u d e < b s d . p o r t . p r e . m k >
. i f ! d e f i n e d ( S L A V E _ O N L Y )
2005-02-19 13:07:46 +01:00
OPTIONS += PAM "Build with PAM support (server only)" off
2007-02-06 16:53:24 +01:00
OPTIONS += LDAP "Build with LDAP authentication support" off
2004-11-23 20:15:12 +01:00
OPTIONS += MIT_KRB5 "Build with MIT's kerberos support" off
2005-02-19 13:07:46 +01:00
OPTIONS += HEIMDAL_KRB5 "Builds with Heimdal kerberos support" off
2004-11-23 20:15:12 +01:00
OPTIONS += OPTIMIZED_CFLAGS "Builds with compiler optimizations (-O3)" off
# to run regression tests:
2005-02-19 13:07:46 +01:00
OPTIONS += TESTS "Allows the use of a \"check\" target (server)" off
2004-11-23 20:15:12 +01:00
OPTIONS += DEBUG "Builds with debugging symbols" off
Upgrade PostgreSQL to 8.0.2. Here's the brief release note:
Over the past several weeks, Tom Lane has been working on replacing
our old Cache Management Alorithm (ARC) with a new, patent free one
(2Q).
In order to reduce the number of 8.x deployments out there that are
using the old manager, we have just released 8.0.2, and encourage
adminstrators to upgrade at their earliest convience.
For those already running 8.x on your production servers, please
note that this upgrade does *NOT* require a dump restore, but due to
a bump in the major version number for the client library (libpq),
it *WILL* require all client applications to be recompiled at the
same time.
For full release info, see
http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-2
Apart from the upgrade, three new config options are added:
A patch (experimental) for supporting proper collation
of utf-8 encoded locales, using IBM's ICU package (devel/icu). See
http://people.freebsd.org/~girgen/postgresql-icu/README.html for more
info.
An optional patch written by Evgen Potemkin, which allows
PostgreSQL to make hierarchical queries à la Oracle [1].
An option is added that allows the use of 64 bit ints to
store dates [2].
PR: ports/79165 [1], ports/76999 [2]
Submitted by: Marcos Tischer Vallim [1], Christian Ullrich [2]
Approved by: ade, seanc (implicit)
2005-04-14 01:15:49 +02:00
# See http://people.freebsd.org/~girgen/postgresql-icu/README.html for more info
2006-12-06 17:50:34 +01:00
#OPTIONS+= ICU "Use ICU for unicode collation (server)" off
Upgrade PostgreSQL to 8.0.2. Here's the brief release note:
Over the past several weeks, Tom Lane has been working on replacing
our old Cache Management Alorithm (ARC) with a new, patent free one
(2Q).
In order to reduce the number of 8.x deployments out there that are
using the old manager, we have just released 8.0.2, and encourage
adminstrators to upgrade at their earliest convience.
For those already running 8.x on your production servers, please
note that this upgrade does *NOT* require a dump restore, but due to
a bump in the major version number for the client library (libpq),
it *WILL* require all client applications to be recompiled at the
same time.
For full release info, see
http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-2
Apart from the upgrade, three new config options are added:
A patch (experimental) for supporting proper collation
of utf-8 encoded locales, using IBM's ICU package (devel/icu). See
http://people.freebsd.org/~girgen/postgresql-icu/README.html for more
info.
An optional patch written by Evgen Potemkin, which allows
PostgreSQL to make hierarchical queries à la Oracle [1].
An option is added that allows the use of 64 bit ints to
store dates [2].
PR: ports/79165 [1], ports/76999 [2]
Submitted by: Marcos Tischer Vallim [1], Christian Ullrich [2]
Approved by: ade, seanc (implicit)
2005-04-14 01:15:49 +02:00
# See http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/76999 for more info
# (requires dump/restore if modified.)
OPTIONS += INTDATE "Builds with 64-bit date/time type (server)" off
2006-12-06 17:50:34 +01:00
# . if (defined(SERVER_ONLY) && defined(WITH_ICU)) || make(makesum)
2008-08-20 02:57:32 +02:00
# USE_AUTOTOOLS= autoconf:262
2006-12-06 17:50:34 +01:00
# CONFIGURE_ARGS+=--with-icu
# LIB_DEPENDS= icudata:${PORTSDIR}/devel/icu
# PATCH_SITES+= http://people.freebsd.org/~girgen/postgresql-icu/:icu
# PATCHFILES+= pg-814-icu-xx-2006-09-25.diff.gz:icu
# . endif
Upgrade PostgreSQL to 8.0.2. Here's the brief release note:
Over the past several weeks, Tom Lane has been working on replacing
our old Cache Management Alorithm (ARC) with a new, patent free one
(2Q).
In order to reduce the number of 8.x deployments out there that are
using the old manager, we have just released 8.0.2, and encourage
adminstrators to upgrade at their earliest convience.
For those already running 8.x on your production servers, please
note that this upgrade does *NOT* require a dump restore, but due to
a bump in the major version number for the client library (libpq),
it *WILL* require all client applications to be recompiled at the
same time.
For full release info, see
http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-2
Apart from the upgrade, three new config options are added:
A patch (experimental) for supporting proper collation
of utf-8 encoded locales, using IBM's ICU package (devel/icu). See
http://people.freebsd.org/~girgen/postgresql-icu/README.html for more
info.
An optional patch written by Evgen Potemkin, which allows
PostgreSQL to make hierarchical queries à la Oracle [1].
An option is added that allows the use of 64 bit ints to
store dates [2].
PR: ports/79165 [1], ports/76999 [2]
Submitted by: Marcos Tischer Vallim [1], Christian Ullrich [2]
Approved by: ade, seanc (implicit)
2005-04-14 01:15:49 +02:00
PATCH_DIST_STRIP = -p1
2004-11-23 20:15:12 +01:00
. i f d e f i n e d ( S E R V E R _ O N L Y ) & & d e f i n e d ( W I T H _ P A M )
2005-02-03 10:30:27 +01:00
CONFIGURE_ARGS += --with-pam
2004-11-23 20:15:12 +01:00
. e n d i f
2007-02-06 16:53:24 +01:00
. i f d e f i n e d ( S E R V E R _ O N L Y ) & & d e f i n e d ( W I T H _ L D A P )
CONFIGURE_ARGS += --with-ldap
USE_OPENLDAP = YES
. e n d i f
Upgrade PostgreSQL to 8.0.2. Here's the brief release note:
Over the past several weeks, Tom Lane has been working on replacing
our old Cache Management Alorithm (ARC) with a new, patent free one
(2Q).
In order to reduce the number of 8.x deployments out there that are
using the old manager, we have just released 8.0.2, and encourage
adminstrators to upgrade at their earliest convience.
For those already running 8.x on your production servers, please
note that this upgrade does *NOT* require a dump restore, but due to
a bump in the major version number for the client library (libpq),
it *WILL* require all client applications to be recompiled at the
same time.
For full release info, see
http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-2
Apart from the upgrade, three new config options are added:
A patch (experimental) for supporting proper collation
of utf-8 encoded locales, using IBM's ICU package (devel/icu). See
http://people.freebsd.org/~girgen/postgresql-icu/README.html for more
info.
An optional patch written by Evgen Potemkin, which allows
PostgreSQL to make hierarchical queries à la Oracle [1].
An option is added that allows the use of 64 bit ints to
store dates [2].
PR: ports/79165 [1], ports/76999 [2]
Submitted by: Marcos Tischer Vallim [1], Christian Ullrich [2]
Approved by: ade, seanc (implicit)
2005-04-14 01:15:49 +02:00
. i f d e f i n e d ( W I T H _ I N T D A T E )
CONFIGURE_ARGS += --enable-integer-datetimes
. e n d i f
2004-11-23 20:15:12 +01:00
. i f ! ( d e f i n e d ( W I T H O U T _ G E T T E X T ) | | d e f i n e d ( W I T H O U T _ N L S ) )
2002-02-19 09:23:22 +01:00
CONFIGURE_ARGS += --enable-nls
PLIST_SUB += GETTEXT = ""
2004-02-05 13:56:00 +01:00
USE_GETTEXT = YES
2004-11-23 20:15:12 +01:00
. e l s e
2003-01-04 02:10:15 +01:00
CONFIGURE_ARGS += --disable-nls
2002-02-19 09:23:22 +01:00
PLIST_SUB += GETTEXT = "@comment "
2004-11-23 20:15:12 +01:00
. e n d i f
2002-02-19 09:23:22 +01:00
2004-11-23 20:15:12 +01:00
. i f d e f i n e d ( W I T H _ O P T I M I Z E D _ C F L A G S )
2003-12-04 13:00:49 +01:00
CFLAGS += -O3 -funroll-loops
2004-11-23 20:15:12 +01:00
. e n d i f
2003-01-04 02:10:15 +01:00
2004-11-23 20:15:12 +01:00
. i f d e f i n e d ( W I T H _ D E B U G )
2005-02-03 10:30:27 +01:00
CONFIGURE_ARGS += --enable-debug
2003-02-06 21:46:51 +01:00
INSTALL_TARGET = install
2004-11-23 20:15:12 +01:00
. e l s e
2003-01-04 02:10:15 +01:00
INSTALL_TARGET = install-strip
2004-11-23 20:15:12 +01:00
. e n d i f
2003-01-04 02:10:15 +01:00
2004-11-23 20:15:12 +01:00
. i f d e f i n e d ( W I T H _ M I T _ K R B 5 )
2005-11-15 00:59:26 +01:00
. i f e x i s t s ( / u s r / l i b / l i b k r b 5 . s o ) | | e x i s t s ( / u s r / b i n / k r b 5 - c o n f i g )
BROKEN = "You must remove heimdal's /usr/bin/krb5-config and /usr/lib/libkrb5.so*, and set NO_KERBEROS=true in /etc/make.conf to build successfully with MIT-KRB"
Welcome to PostgreSQL 8.1.
The new release includes performance improvements and advanced SQL
features which will support bigger data warehouses, higher-volume
transaction processing, and more complex distributed enterprise
software.
Major new features in this release include:
Roles:
PostgreSQL now supports database roles, which simplify the
management of large numbers of users with complex
overlapping database rights.
IN/OUT Parameters:
PostgreSQL functions now support IN, OUT and INOUT
parameters, which substantially improves support of complex
business logic for J2EE and .NET applications.
Two-Phase Commit (2PC):
Long in demand for WAN applications and heterogeneous data
centers using PostgreSQL, this feature allows
ACID-compliant transactions across widely separated
servers.
Some Performance Enhancements found in this release include:
Improved Multiprocessor (SMP) Performance:
The buffer manager for 8.1 has been enhanced to scale almost
linearly with the number of processors, leading to significant
performance gains on 8-way, 16-way, dual-core, and multi-core
CPU servers.
Bitmap Scan:
Indexes will be dynamically converted to bitmaps in memory when
appropriate, giving up to twenty times faster index performance
on complex queries against very large tables.
Table Partitioning:
The query planner is now able to avoid scanning whole sections
of a large table using a technique known as Constraint
Exclusion.
Shared Row Locking:
PostgreSQL's "better than row-level locking" now supports even
higher levels of concurrency through the addition of shared
row locks for foreign keys.
For a more complete listing of changes in this release, please see the
Release Notes visible at:
http://www.postgresql.org/docs/current/static/release.html#RELEASE-8-1
2005-11-10 03:23:38 +01:00
. e n d i f
2005-11-15 00:59:26 +01:00
# Allow defining a home built MIT Kerberos by setting KRB5_HOME
. i f d e f i n e d ( K R B 5 _ H O M E ) & & e x i s t s ( $ { K R B 5 _ H O M E } / l i b / l i b g s s a p i _ k r b 5 . a ) & & e x i s t s ( $ { K R B 5 _ H O M E } / b i n / k r b 5 - c o n f i g )
CONFIGURE_ARGS += --with-krb5
. e l s e
2003-12-05 22:22:42 +01:00
LIB_DEPENDS += krb5.3:${ PORTSDIR } /security/krb5
2005-11-15 00:59:26 +01:00
CONFIGURE_ARGS += --with-krb5
. e n d i f
2004-11-23 20:15:12 +01:00
. e n d i f
2003-01-04 02:10:15 +01:00
2004-11-23 20:15:12 +01:00
. i f d e f i n e d ( W I T H _ H E I M D A L _ K R B 5 )
2005-11-15 00:59:26 +01:00
# Allow defining a home built Heimdal Kerberos by setting HEIMDAL_HOME
. i f d e f i n e d ( H E I M D A L _ H O M E ) & & e x i s t s ( $ { H E I M D A L _ H O M E } / l i b / l i b g s s a p i . a ) & & e x i s t s ( $ { H E I M D A L _ H O M E } / b i n / k r b 5 - c o n f i g )
CONFIGURE_ARGS += --with-krb5
. e l s e
# Postgresql apps will not link properly when libpq is linked with base heimdal in /usr,
# so we always use the heimdal port. See
Welcome to PostgreSQL 8.1.
The new release includes performance improvements and advanced SQL
features which will support bigger data warehouses, higher-volume
transaction processing, and more complex distributed enterprise
software.
Major new features in this release include:
Roles:
PostgreSQL now supports database roles, which simplify the
management of large numbers of users with complex
overlapping database rights.
IN/OUT Parameters:
PostgreSQL functions now support IN, OUT and INOUT
parameters, which substantially improves support of complex
business logic for J2EE and .NET applications.
Two-Phase Commit (2PC):
Long in demand for WAN applications and heterogeneous data
centers using PostgreSQL, this feature allows
ACID-compliant transactions across widely separated
servers.
Some Performance Enhancements found in this release include:
Improved Multiprocessor (SMP) Performance:
The buffer manager for 8.1 has been enhanced to scale almost
linearly with the number of processors, leading to significant
performance gains on 8-way, 16-way, dual-core, and multi-core
CPU servers.
Bitmap Scan:
Indexes will be dynamically converted to bitmaps in memory when
appropriate, giving up to twenty times faster index performance
on complex queries against very large tables.
Table Partitioning:
The query planner is now able to avoid scanning whole sections
of a large table using a technique known as Constraint
Exclusion.
Shared Row Locking:
PostgreSQL's "better than row-level locking" now supports even
higher levels of concurrency through the addition of shared
row locks for foreign keys.
For a more complete listing of changes in this release, please see the
Release Notes visible at:
http://www.postgresql.org/docs/current/static/release.html#RELEASE-8-1
2005-11-10 03:23:38 +01:00
# http://lists.freebsd.org/pipermail/freebsd-stable/2005-October/018809.html
2008-01-07 14:51:57 +01:00
LIB_DEPENDS += krb5.23:${ PORTSDIR } /security/heimdal
2005-11-15 00:59:26 +01:00
CONFIGURE_ARGS += --with-krb5
. e n d i f
2004-11-23 20:15:12 +01:00
. e n d i f
2003-01-04 02:10:15 +01:00
2004-11-23 20:15:12 +01:00
. e n d i f # !SLAVE_ONLY
. i f d e f i n e d ( C L I E N T _ O N L Y )
2005-01-31 01:36:16 +01:00
MAN1 = clusterdb.1 createdb.1 createlang.1 createuser.1 \
dropdb.1 droplang.1 dropuser.1 ecpg.1 initdb.1 \
ipcclean.1 pg_config.1 pg_controldata.1 pg_ctl.1 \
pg_dump.1 pg_dumpall.1 pg_resetxlog.1 pg_restore.1 \
Welcome to PostgreSQL 8.1.
The new release includes performance improvements and advanced SQL
features which will support bigger data warehouses, higher-volume
transaction processing, and more complex distributed enterprise
software.
Major new features in this release include:
Roles:
PostgreSQL now supports database roles, which simplify the
management of large numbers of users with complex
overlapping database rights.
IN/OUT Parameters:
PostgreSQL functions now support IN, OUT and INOUT
parameters, which substantially improves support of complex
business logic for J2EE and .NET applications.
Two-Phase Commit (2PC):
Long in demand for WAN applications and heterogeneous data
centers using PostgreSQL, this feature allows
ACID-compliant transactions across widely separated
servers.
Some Performance Enhancements found in this release include:
Improved Multiprocessor (SMP) Performance:
The buffer manager for 8.1 has been enhanced to scale almost
linearly with the number of processors, leading to significant
performance gains on 8-way, 16-way, dual-core, and multi-core
CPU servers.
Bitmap Scan:
Indexes will be dynamically converted to bitmaps in memory when
appropriate, giving up to twenty times faster index performance
on complex queries against very large tables.
Table Partitioning:
The query planner is now able to avoid scanning whole sections
of a large table using a technique known as Constraint
Exclusion.
Shared Row Locking:
PostgreSQL's "better than row-level locking" now supports even
higher levels of concurrency through the addition of shared
row locks for foreign keys.
For a more complete listing of changes in this release, please see the
Release Notes visible at:
http://www.postgresql.org/docs/current/static/release.html#RELEASE-8-1
2005-11-10 03:23:38 +01:00
postgres.1 postmaster.1 psql.1 reindexdb.1 vacuumdb.1
2005-01-31 01:36:16 +01:00
MAN7 = abort.7 alter_aggregate.7 alter_conversion.7 alter_database.7 \
alter_domain.7 alter_function.7 alter_group.7 \
alter_index.7 alter_language.7 alter_operator_class.7 \
Welcome to PostgreSQL 8.1.
The new release includes performance improvements and advanced SQL
features which will support bigger data warehouses, higher-volume
transaction processing, and more complex distributed enterprise
software.
Major new features in this release include:
Roles:
PostgreSQL now supports database roles, which simplify the
management of large numbers of users with complex
overlapping database rights.
IN/OUT Parameters:
PostgreSQL functions now support IN, OUT and INOUT
parameters, which substantially improves support of complex
business logic for J2EE and .NET applications.
Two-Phase Commit (2PC):
Long in demand for WAN applications and heterogeneous data
centers using PostgreSQL, this feature allows
ACID-compliant transactions across widely separated
servers.
Some Performance Enhancements found in this release include:
Improved Multiprocessor (SMP) Performance:
The buffer manager for 8.1 has been enhanced to scale almost
linearly with the number of processors, leading to significant
performance gains on 8-way, 16-way, dual-core, and multi-core
CPU servers.
Bitmap Scan:
Indexes will be dynamically converted to bitmaps in memory when
appropriate, giving up to twenty times faster index performance
on complex queries against very large tables.
Table Partitioning:
The query planner is now able to avoid scanning whole sections
of a large table using a technique known as Constraint
Exclusion.
Shared Row Locking:
PostgreSQL's "better than row-level locking" now supports even
higher levels of concurrency through the addition of shared
row locks for foreign keys.
For a more complete listing of changes in this release, please see the
Release Notes visible at:
http://www.postgresql.org/docs/current/static/release.html#RELEASE-8-1
2005-11-10 03:23:38 +01:00
alter_role.7 \
2005-01-31 01:36:16 +01:00
alter_schema.7 alter_sequence.7 alter_table.7 \
alter_trigger.7 alter_user.7 analyze.7 begin.7 \
checkpoint.7 close.7 cluster.7 comment.7 commit.7 \
Welcome to PostgreSQL 8.1.
The new release includes performance improvements and advanced SQL
features which will support bigger data warehouses, higher-volume
transaction processing, and more complex distributed enterprise
software.
Major new features in this release include:
Roles:
PostgreSQL now supports database roles, which simplify the
management of large numbers of users with complex
overlapping database rights.
IN/OUT Parameters:
PostgreSQL functions now support IN, OUT and INOUT
parameters, which substantially improves support of complex
business logic for J2EE and .NET applications.
Two-Phase Commit (2PC):
Long in demand for WAN applications and heterogeneous data
centers using PostgreSQL, this feature allows
ACID-compliant transactions across widely separated
servers.
Some Performance Enhancements found in this release include:
Improved Multiprocessor (SMP) Performance:
The buffer manager for 8.1 has been enhanced to scale almost
linearly with the number of processors, leading to significant
performance gains on 8-way, 16-way, dual-core, and multi-core
CPU servers.
Bitmap Scan:
Indexes will be dynamically converted to bitmaps in memory when
appropriate, giving up to twenty times faster index performance
on complex queries against very large tables.
Table Partitioning:
The query planner is now able to avoid scanning whole sections
of a large table using a technique known as Constraint
Exclusion.
Shared Row Locking:
PostgreSQL's "better than row-level locking" now supports even
higher levels of concurrency through the addition of shared
row locks for foreign keys.
For a more complete listing of changes in this release, please see the
Release Notes visible at:
http://www.postgresql.org/docs/current/static/release.html#RELEASE-8-1
2005-11-10 03:23:38 +01:00
commit_prepared.7 \
2005-01-31 01:36:16 +01:00
copy.7 create_aggregate.7 create_cast.7 \
create_constraint_trigger.7 create_conversion.7 \
create_database.7 create_domain.7 create_function.7 \
create_group.7 create_index.7 create_language.7 \
create_operator.7 create_operator_class.7 \
Welcome to PostgreSQL 8.1.
The new release includes performance improvements and advanced SQL
features which will support bigger data warehouses, higher-volume
transaction processing, and more complex distributed enterprise
software.
Major new features in this release include:
Roles:
PostgreSQL now supports database roles, which simplify the
management of large numbers of users with complex
overlapping database rights.
IN/OUT Parameters:
PostgreSQL functions now support IN, OUT and INOUT
parameters, which substantially improves support of complex
business logic for J2EE and .NET applications.
Two-Phase Commit (2PC):
Long in demand for WAN applications and heterogeneous data
centers using PostgreSQL, this feature allows
ACID-compliant transactions across widely separated
servers.
Some Performance Enhancements found in this release include:
Improved Multiprocessor (SMP) Performance:
The buffer manager for 8.1 has been enhanced to scale almost
linearly with the number of processors, leading to significant
performance gains on 8-way, 16-way, dual-core, and multi-core
CPU servers.
Bitmap Scan:
Indexes will be dynamically converted to bitmaps in memory when
appropriate, giving up to twenty times faster index performance
on complex queries against very large tables.
Table Partitioning:
The query planner is now able to avoid scanning whole sections
of a large table using a technique known as Constraint
Exclusion.
Shared Row Locking:
PostgreSQL's "better than row-level locking" now supports even
higher levels of concurrency through the addition of shared
row locks for foreign keys.
For a more complete listing of changes in this release, please see the
Release Notes visible at:
http://www.postgresql.org/docs/current/static/release.html#RELEASE-8-1
2005-11-10 03:23:38 +01:00
create_role.7 \
2005-01-31 01:36:16 +01:00
create_rule.7 create_schema.7 create_sequence.7 \
create_table.7 create_table_as.7 create_trigger.7 \
2005-02-06 22:59:13 +01:00
create_type.7 create_user.7 create_view.7 deallocate.7 \
declare.7 delete.7 \
2005-01-31 01:36:16 +01:00
drop_aggregate.7 drop_cast.7 drop_conversion.7 \
drop_database.7 drop_domain.7 drop_function.7 \
drop_group.7 drop_index.7 drop_language.7 \
2006-12-06 17:50:34 +01:00
drop_operator.7 drop_operator_class.7 drop_owned.7 \
drop_role.7 drop_rule.7 \
2005-02-06 22:59:13 +01:00
drop_schema.7 drop_sequence.7 drop_table.7 drop_trigger.7 \
2005-01-31 01:36:16 +01:00
drop_type.7 drop_user.7 drop_view.7 end.7 execute.7 \
explain.7 fetch.7 grant.7 insert.7 listen.7 load.7 \
Welcome to PostgreSQL 8.1.
The new release includes performance improvements and advanced SQL
features which will support bigger data warehouses, higher-volume
transaction processing, and more complex distributed enterprise
software.
Major new features in this release include:
Roles:
PostgreSQL now supports database roles, which simplify the
management of large numbers of users with complex
overlapping database rights.
IN/OUT Parameters:
PostgreSQL functions now support IN, OUT and INOUT
parameters, which substantially improves support of complex
business logic for J2EE and .NET applications.
Two-Phase Commit (2PC):
Long in demand for WAN applications and heterogeneous data
centers using PostgreSQL, this feature allows
ACID-compliant transactions across widely separated
servers.
Some Performance Enhancements found in this release include:
Improved Multiprocessor (SMP) Performance:
The buffer manager for 8.1 has been enhanced to scale almost
linearly with the number of processors, leading to significant
performance gains on 8-way, 16-way, dual-core, and multi-core
CPU servers.
Bitmap Scan:
Indexes will be dynamically converted to bitmaps in memory when
appropriate, giving up to twenty times faster index performance
on complex queries against very large tables.
Table Partitioning:
The query planner is now able to avoid scanning whole sections
of a large table using a technique known as Constraint
Exclusion.
Shared Row Locking:
PostgreSQL's "better than row-level locking" now supports even
higher levels of concurrency through the addition of shared
row locks for foreign keys.
For a more complete listing of changes in this release, please see the
Release Notes visible at:
http://www.postgresql.org/docs/current/static/release.html#RELEASE-8-1
2005-11-10 03:23:38 +01:00
lock.7 move.7 notify.7 prepare.7 prepare_transaction.7 \
2006-12-06 17:50:34 +01:00
reassign_owned.7 reindex.7 reset.7 \
Welcome to PostgreSQL 8.1.
The new release includes performance improvements and advanced SQL
features which will support bigger data warehouses, higher-volume
transaction processing, and more complex distributed enterprise
software.
Major new features in this release include:
Roles:
PostgreSQL now supports database roles, which simplify the
management of large numbers of users with complex
overlapping database rights.
IN/OUT Parameters:
PostgreSQL functions now support IN, OUT and INOUT
parameters, which substantially improves support of complex
business logic for J2EE and .NET applications.
Two-Phase Commit (2PC):
Long in demand for WAN applications and heterogeneous data
centers using PostgreSQL, this feature allows
ACID-compliant transactions across widely separated
servers.
Some Performance Enhancements found in this release include:
Improved Multiprocessor (SMP) Performance:
The buffer manager for 8.1 has been enhanced to scale almost
linearly with the number of processors, leading to significant
performance gains on 8-way, 16-way, dual-core, and multi-core
CPU servers.
Bitmap Scan:
Indexes will be dynamically converted to bitmaps in memory when
appropriate, giving up to twenty times faster index performance
on complex queries against very large tables.
Table Partitioning:
The query planner is now able to avoid scanning whole sections
of a large table using a technique known as Constraint
Exclusion.
Shared Row Locking:
PostgreSQL's "better than row-level locking" now supports even
higher levels of concurrency through the addition of shared
row locks for foreign keys.
For a more complete listing of changes in this release, please see the
Release Notes visible at:
http://www.postgresql.org/docs/current/static/release.html#RELEASE-8-1
2005-11-10 03:23:38 +01:00
revoke.7 rollback.7 rollback_prepared.7 select .7 \
select_into.7 set.7 \
set_constraints.7 set_role.7 set_transaction.7 show.7 \
2005-01-31 01:36:16 +01:00
set_session_authorization.7 start_transaction.7 \
truncate.7 unlisten.7 update.7 vacuum.7 \
alter_operator.7 alter_tablespace.7 alter_type.7 \
create_tablespace.7 drop_tablespace.7 \
release_savepoint.7 rollback_to_savepoint.7 \
2006-12-06 17:50:34 +01:00
savepoint.7 values.7
2004-11-23 20:15:12 +01:00
. e n d i f
1997-04-09 17:30:55 +02:00
2004-11-23 20:15:12 +01:00
. i f d e f i n e d ( S E R V E R _ O N L Y )
2003-01-04 02:10:15 +01:00
pre-everything ::
2003-06-02 03:44:03 +02:00
@${ SH } ${ PKGINSTALL } ${ PORTNAME } BACKUPWARNING
2003-02-06 21:46:51 +01:00
. e n d i f
2004-11-23 20:15:12 +01:00
. i f ! d e f i n e d ( N O _ B U I L D )
2005-01-31 01:36:16 +01:00
pre-configure :
. i f d e f i n e d ( W I T H _ M I T _ K R B 5 ) & & d e f i n e d ( W I T H _ H E I M D A L _ K R B 5 )
@${ ECHO } "MIT's and Heimdal Kerberos are mutually exclusive."
@${ ECHO } "Please choose one or the other."
@exit 1
. e n d i f
2004-11-23 20:15:12 +01:00
do-build :
@ cd ${ WRKSRC } /src/backend ; \
${ GMAKE } ../../src/include/parser/parse.h ../../src/include/utils/fmgroids.h
@ for dir in ${ BUILD_DIRS } ; do \
cd ${ WRKSRC } /$$ { dir} && ${ SETENV } ${ MAKE_ENV } ${ GMAKE } ; \
done
2006-12-06 17:50:34 +01:00
. i f e x i s t s ( $ { F I L E S D I R } / p k g - m e s s a g e $ { P K G N A M E S U F F I X } . i n )
SUB_FILES += pkg-message${ PKGNAMESUFFIX }
PKGMESSAGE = ${ WRKSRC } /pkg-message${ PKGNAMESUFFIX }
2004-11-23 20:15:12 +01:00
. e n d i f
2003-02-06 21:46:51 +01:00
. e n d i f
2002-02-19 09:23:22 +01:00
2004-11-23 20:15:12 +01:00
. i f d e f i n e d ( S E R V E R _ O N L Y )
2006-05-23 23:18:58 +02:00
pre-su-install :
2002-02-19 09:23:22 +01:00
@ ${ SETENV } PKG_PREFIX = ${ PREFIX } \
2003-06-02 03:44:03 +02:00
${ SH } ${ PKGINSTALL } ${ PORTNAME } PRE-INSTALL
2000-12-11 04:22:07 +01:00
. e n d i f
1997-04-09 17:30:55 +02:00
2004-11-23 20:15:12 +01:00
. i f ! d e f i n e d ( N O _ B U I L D )
do-install :
@for dir in ${ INSTALL_DIRS } ; do \
cd ${ WRKSRC } /$$ { dir} && \
${ SETENV } ${ MAKE_ENV } ${ GMAKE } ${ INSTALL_TARGET } ; \
done
. i f d e f i n e d ( S E R V E R _ O N L Y )
2005-01-31 01:36:16 +01:00
@ ${ MKDIR } ${ PREFIX } /share/postgresql
. f o r i i n p r o f i l e c s h r c
2006-12-06 17:50:34 +01:00
${ INSTALL_DATA } ${ WRKDIR } /dot.$i ${ PREFIX } /share/postgresql/dot.$i .dist; \
${ INSTALL_DATA } -o pgsql -g pgsql ${ WRKDIR } /dot.$i ~pgsql/dot.$i .dist ; \
2001-04-21 13:34:34 +02:00
if [ ! -f ~pgsql/.$i ] ; then \
2006-12-06 17:50:34 +01:00
${ CP } -p ~pgsql/dot.$i .dist ~pgsql/.$i ; \
1997-06-14 21:40:05 +02:00
fi
2005-01-31 01:36:16 +01:00
. e n d f o r
2006-12-06 17:50:34 +01:00
@ ${ CHOWN } -R pgsql:pgsql ~pgsql/. ; \
2004-11-23 20:15:12 +01:00
${ MKDIR } ${ PREFIX } /etc/periodic/daily ; \
2005-02-03 10:30:27 +01:00
${ INSTALL_SCRIPT } ${ FILESDIR } /502.pgsql \
2004-11-23 20:15:12 +01:00
${ PREFIX } /etc/periodic/daily
. e n d i f # SERVER_ONLY
2005-05-11 02:40:15 +02:00
. i f d e f i n e d ( C L I E N T _ O N L Y )
@ cd ${ WRKSRC } /src && ${ SETENV } ${ MAKE_ENV } ${ GMAKE } install-local
. e n d i f
2004-11-23 20:15:12 +01:00
@ if [ -r ${ PKGMESSAGE } ] ; then \
2005-01-31 01:36:16 +01:00
${ MKDIR } ${ DOCSDIR } ; \
${ INSTALL_DATA } ${ PKGMESSAGE } ${ DOCSDIR } /README${ PKGNAMESUFFIX } ; \
2004-11-23 20:15:12 +01:00
${ ECHO } "======================================================================" ; \
${ CAT } ${ PKGMESSAGE } ; \
${ ECHO } "======================================================================" ; \
fi
. e n d i f # !NO_BUILD
1997-04-09 17:30:55 +02:00
2004-11-23 20:15:12 +01:00
. i f d e f i n e d ( S E R V E R _ O N L Y ) & & d e f i n e d ( W I T H _ T E S T S )
2003-02-06 21:46:51 +01:00
check :
@if [ ` id -u` != 0 ] ; then \
${ ECHO } "Running postgresql regressions tests" ; \
cd ${ WRKSRC } ; ${ GMAKE } check ; \
else \
${ ECHO } "You cannot run regression tests when postgresql is built as user root." ; \
${ ECHO } "Clean and rebuild the port as a regular user to run the tests." ; \
fi
. e n d i f
2003-06-02 03:44:03 +02:00
. i n c l u d e < b s d . p o r t . p o s t . m k >
