summaryrefslogtreecommitdiff
path: root/databases/postgresql-lib
AgeCommit message (Collapse)AuthorFilesLines
2004-03-26PKGREVISION bump after openssl-security-fix-update to 0.9.6m.wiz3-4/+6
Buildlink files: RECOMMENDED version changed to current version.
2004-03-18Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properlyjlam1-3/+2
by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
2004-03-05Reorder location and setting of BUILDLINK_PACKAGES to match templatejlam1-3/+6
buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
2004-02-01Fix typo in previous commit (LIBEPQ -> LIBPQ). This closes PR pkg/24290.xtraeme1-2/+2
2004-01-30Use PLIST_SUBST in two files, which were not installed in FreeBSD.xtraeme2-4/+12
2004-01-24Append to BUILDLINK_DEPENDS.<pkg> instead of setting a default value. Injlam1-2/+2
the normal case when BUILDLINK_DEPENDS.<pkg> isn't specified, it receives a value only once due to the multiple inclusion protection in the bulldlink3.mk files. In the case where a package includes several buildlink3.mk files that each want a slightly different version of another dependency, having BUILDLINK_DEPENDS.<pkg> be a list allows for the strictest <pkg> dependency to be matched.
2004-01-21bl3ifyjlam1-3/+6
2004-01-21Adding and removing the pgsql symlink must take place at VIEW-* time sincejlam1-3/+3
the symlink isn't tracked in the PLIST and won't be correctly removed from any views during instance deletion from a view.
2004-01-21Move @exec/@unexec PLIST actions into a INSTALL file.jlam3-7/+19
2004-01-20Fix spelling of PKGREVISION.jlam1-2/+2
2004-01-20Remove USE_BUILDLINK2 from Makefile.common and distribute the setting tojlam1-1/+3
all of the package Makefiles that include Makefile.common.
2004-01-05Use S/+$// instead of C/\+$// to save a backslash. Very highlyjlam1-2/+2
recommended by seb :)
2004-01-04Re-arrange to match example buildlink3.mk file in bsd.buildlink3.mk.jlam1-10/+7
2004-01-03Initial sprinkling of work-in-progress buildlink3.mk files for using thejlam1-0/+22
buildlink3 framework.
2003-11-12PKGREVISION++ after openssl update.jschauma1-1/+2
2003-09-18Specify the category when including other files and when depending on otherjmmv1-2/+2
packages. From PR pkg/21864 by ccatrian at eml.cc.
2003-05-06Drop trailing whitespace. Ok'ed by wiz.jmmv1-4/+4
2003-03-25Add in SVR4 pkg names.cjep1-1/+2
2003-01-05Updated databases/postgresql to 7.3.1.jlam3-373/+371
================================================================== | NOTE: A dump-and-restore is required to update your databases | | if you wish to update postgresql-server. If your | | application examines the system catalogs, additional | | changes will be required due to the introduction of | | schemas in 7.3; for more information, see: | | | | http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 | ================================================================== Major changes from version 7.2.3 include: Schemas Schemas allow users to create objects in separate namespaces, so two people or applications can have tables with the same name. There is also a public schema for shared tables. Table/index creation can be restricted by removing permissions on the public schema. Drop Column PostgreSQL now supports the ALTER TABLE ... DROP COLUMN functionality. Table Functions Functions returning multiple rows and/or multiple columns are now much easier to use than before. You can call such a "table function" in the SELECT FROM clause, treating its output like a table. Also, PL/pgSQL functions can now return sets. Prepared Queries PostgreSQL now supports prepared queries, for improved performance. Dependency Tracking PostgreSQL now records object dependencies, which allows improvements in many areas. "DROP" statements now take either CASCADE or RESTRICT to control whether dependent objects are also dropped. Privileges Functions and procedural languages now have privileges, and functions can be defined to run with the privileges of their creator. Internationalization Both multibyte and locale support are now always enabled. Logging A variety of logging options have been enhanced. Interfaces A large number of interfaces have been moved to http://gborg.postgresql.org where they can be developed and released independently. Functions/Identifiers By default, functions can now take up to 32 parameters, and identifiers can be up to 63 bytes long. Also, OPAQUE is now deprecated: there are specific "pseudo-datatypes" to represent each of the former meanings of OPAQUE in function argument and result types.
2002-10-21Unused.wiz1-41/+0
2002-10-19Update databases/postgresql to version 7.2.3.jlam1-17/+9
This has a variety of fixes from 7.2.2, including fixes to prevent possible data loss. A dump/restore is *not* required for those running 7.2.X. Changes from version 7.2.2 include: Prevent possible compressed transaction log loss (Tom) Prevent non-superuser from increasing most recent vacuum info (Tom) Handle pre-1970 date values in newer versions of glibc (Tom) Fix possible hang during server shutdown Prevent spinlock hangs on SMP PPC machines (Tomoyuki Niijima) Fix pg_dump to properly dump FULL JOIN USING (Tom)
2002-08-25Merge changes in packages from the buildlink2 branch that havejlam2-4/+30
buildlink2.mk files back into the main trunk. This provides sufficient buildlink2 infrastructure to start merging other packages from the buildlink2 branch that have already been converted to use the buildlink2 framework.
2002-04-05add a few includes that are needed to build gtksqlhubertf1-2/+3
2002-04-04Update postgresql and related packages to 7.2. Thanks to Michael Graffjlam2-340/+355
<explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-02-15mkdir -> ${MKDIR}skrll1-2/+2
rmdir -> ${RMDIR} rm -> ${RM} (${RM} added to PLIST_SUBST) chmod -> ${CHMOD} chown -> ${CHOWN}
2001-12-03Use PKGREVISION to manage the package-specific version number when itjlam1-3/+2
differs from the distfile version number. G/C some the unused variables in postgresql/Makefile.common related to the old way of handling version numbers.
2001-11-01Move pkg/ files into package's toplevel directoryzuntum2-1/+1
2001-07-29Work arround build problem under Solaris. Fixes PR pkg/13021 bytron1-1/+8
Jeff Rizzo.
2001-07-27Add dir_DEFAULT setting used by EVAL_PREFIX logic to set the defaultjlam1-1/+2
installation directory in case the package isn't installed.
2001-07-20Mechanical changes to buildlink.mk files to use EVAL_PREFIX to setjlam1-2/+2
BUILDLINK_PREFIX.<pkgname>. This allows buildlink to find X11BASE packages regardless of whether they were installed before or after xpkgwedge was installed. Idea by Alistair Crooks <agc@pkgsrc.org>.
2001-07-01Move inclusion of bsd.buildlink.mk to start of file.jlam1-3/+3
2001-06-23Generalize how the dependency pattern may be specified. Instead of justjlam1-8/+5
FOO_REQD=1.0 being converted to foo>=1.0, one can now directly specify the dependency pattern as FOO_DEPENDS=foo>=1.0. This allows things like JPEG_DEPENDS=jpeg-6b, or fancier expressions like for postgresql-lib. Change existing FOO_REQD definitions in Makefiles to FOO_DEPENDS.
2001-06-21Add buildlink.mk files for use by other package Makefiles.jlam1-0/+42
2001-06-21Convert to use buildlink.mk files and mark as USE_BUILDLINK_ONLY.jlam1-1/+3
2001-05-14postgresql-lib: PostgreSQL database headers and librariesjlam4-0/+403
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-23 13:25:54 +0000