summaryrefslogtreecommitdiff
path: root/databases/postgresql80-server/pkg-plist-server
Commit message (Collapse)AuthorAgeFilesLines
* Updates of the PostgreSQL portsPalle Girgensohn2008-06-121-0/+3
| | | | | | | | | | | | | | | | | | | | Updates for all maintained versions of PostgreSQL are available today: 8.3.3, 8.2.9, 8.1.13, 8.0.17 and 7.4.21. These releases fix more than two dozen minor issues reported and patched over the last few months. All PostgreSQL users should plan to update at their earliest convenience. People in affected time zones, in particular, should upgrade as soon as possible. Release Notes: http://www.postgresql.org/docs/8.3/static/release.html Also, fix umask error in periodic script [1]. PR: ports/124457 [1] Submitted by: Alexandre Perrin Notes: svn path=/head/; revision=214728
* Update all PostgreSQL ports to latest versions.Palle Girgensohn2008-01-071-0/+2
| | | | | | | | | | This includes a bunch of security fixes: CVE-2007-6067, CVE-2007-4772, CVE-2007-6601, CVE-2007-6600 and CVE-2007-4769. Security: http://www.postgresql.org/about/news.905 Notes: svn path=/head/; revision=205167
* Update PostgreSQL ports to the latest patch releases.Palle Girgensohn2007-09-171-0/+1
| | | | | | | PR: ports/104075 Notes: svn path=/head/; revision=199626
* - Welcome X.org 7.2 \o/.Florent Thoumie2007-05-191-14/+0
| | | | | | | | - Set X11BASE to ${LOCALBASE} for recent ${OSVERSION}. - Bump PORTREVISION for ports intalling files in ${X11BASE}. Notes: svn path=/head/; revision=191544
* Update PostgreSQL to 7.3.19, 7.4.17, 8.0.13, 8.1.9 and 8.2.4 respectively:Palle Girgensohn2007-04-231-457/+463
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The PostgreSQL Global Development Group has released updated versions for PostgreSQL 8.2 and all back versions to patch a privilege escalation exploit in SECURITY DEFINER functions. All users of this feature are urged to update to the latest minor version and follow instructions on securing these functions as soon as possible. This minor release also contains other fixes, so all users should plan to deploy it. Once you have updated, additional steps are required to secure your database against the exploit. Please read the release notes at http://www.postgresql.org/docs/8.2/static/release.html and the TechDocs article at http://www.postgresql.org/docs/techdocs.77 on how to lock down your security definer functions, if you use them. As always, application of a minor release does not require a dump and reload of the database. The frequency of security fixes recently is a result of increased scrutiny of the PostgreSQL code by government agencies and security-conscious companies. Rapid turnaround on security patches is key to keeping PostgreSQL the most secure SQL database. Your work and vigilance in applying the latest security updates ensures that there will never be a PostgreSQL "worm". http://www.postgresql.org/docs/8.2/static/release-8-2-4.html http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-9 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-13 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-17 http://www.postgresql.org/docs/techdocs.77 Security: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-2138 Notes: svn path=/head/; revision=190743
* Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17.Palle Girgensohn2007-01-091-23/+91
| | | | | | | | | | | | | | | | | | | | | Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server Notes: svn path=/head/; revision=181869
* Update PostgreSQL to latest versions: 8.1.5, 8.0.9, 7.4.14 and 7.3.16.Palle Girgensohn2006-11-081-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | Release notes: 8.1.5 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-5 8.0.9 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-9 7.4.14 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-14 7.3.16 http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-16 Change name of the rc script from '010.pgsql.sh' to 'postgresql' Add optional hierachy patch added for 7.4 and 8.1 ports. Chase heimdal libs update [reported by several] For 8.1+ the port enables autovacuum in ~pgsql/postgresql.conf when running initdb Cleanup the ports, moving pkg-message-* to files/pkg-message-*.in and files/pgsql.sh.tmpl to files/postgresql.in. [ports/97767] PR: ports/97767, submitted by delphij@FreeBSD.org Notes: svn path=/head/; revision=176828
* eplace ugly "@unexec rmdir %D... 2>/dev/null || true" with @dirrmtryEdwin Groothuis2006-01-221-20/+20
| | | | | | | | Approved by: krion@ PR: ports/88711 (related) Notes: svn path=/head/; revision=154134
* Upgrade to 8.0.4Palle Girgensohn2005-10-051-0/+2
| | | | | | | | For more info about this release, please see http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-4 Notes: svn path=/head/; revision=144239
* Fixing problems with the recent security patch: When bison was notPalle Girgensohn2005-05-111-0/+1
| | | | | | | | | | | | | | | | | | | | installed, the patched gram.y file would not be used and the security patch would be a no-op. Also, I've had reports of compilation errors related to bison. Since checking for the correct version of bison is hard and error prone, I'm doing what the postgresql distribution does - patching the yacc:ed .c file to get rid of the building dependency. Bumping portrevision of -server. Pointy hat to: me Noticed by: Mike Harding and others Security: http://www.vuxml.org/freebsd/6b4b0b3f-8127-11d9-a9e7-0001020eed82.html Approved by: seanc (implicit) Notes: svn path=/head/; revision=135025
* In order to address a potential security hole recently identified withPalle Girgensohn2005-02-031-1/+1
| | | | | | | | | | | | | | | | | | | | | | the "LOAD" option, the PostgreSQL Global Development Group is announcing the release of new versions of PostgreSQL. Update to 7.3.9, 7.4.7 & 8.0.1. Take the opportunity to reset PORTREVISION of slave ports. Back out name change of startup script. The new script uses rc.subr(8), and as such also uses rcorder(8). But, rcorder does not exist in FreeBSD 4.x. Hence rename the script it back to the top of the directory list. [1] The periodic script should of course be executable. [2] [1] Noted by Niels Chr. Bank-Pedersen <ncbp at bank-pedersen dot dk> [2] Noted by Fritz Heinrichmeyer <fritz.heinrichmeyer at fernuni-hagen dot de> Notes: svn path=/head/; revision=127966
* Say hello to postgresql-8.0. Some of the highlights of the new versionPalle Girgensohn2005-01-311-347/+603
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | are savepoints (within transactions), point-in-time recovery and tablespaces. Check out the release notes and the shiny new PostgreSQL.org website at: http://www.PostgreSQL.org/docs/8.0/static/release.html#RELEASE-8-0 The port uses the new postgresql ports' layout and is split into a server and a client part. The following knobs can be used by ports depending on PostgreSQL: # USE_PGSQL - Add PostgreSQL client dependency. # If no version is given (by the maintainer via the port or # by the user via defined variable), try to find the # currently installed version. Fall back to default if # necessary (PostgreSQL-7.4 = 74). # DEFAULT_PGSQL_VER # - PostgreSQL default version. Can be overridden within a port. # Default: 74. # WANT_PGSQL_VER # - Maintainer can set an arbitrary version of PostgreSQL by # using it. # BROKEN_WITH_PGSQL # - This variable can be defined if the ports doesn't support # one or more versions of PostgreSQL. PR: 75344 Approved by: portmgr@ (kris), ade & sean (mentors) Notes: svn path=/head/; revision=127738
* Another step along the road to the postgresql new world order.Ade Lovett2004-11-231-0/+411
Note that none of these ports are (yet) hooked into the tree, and will not compile unless you set a specific environmental variable. This should be warning enough to leave well alone for now :) Submitted by: maintainer Notes: svn path=/head/; revision=122238
generated by cgit v1.3 (git 2.53.0) at 2026-09-02 12:54:12 +0000