BSD Ports

Vulnerable: version 17.11 is affected by 1 known vulnerability. See below.

databases/postgresql17-server 17.11 DragonFly

PostgreSQL is the most advanced open-source database available anywhere

System
DragonFly
Repository
DPorts
Maintainer
[email protected] (as in FreeBSD)
License
PostgreSQL
Categories
databases
Package size
6117.7 KiB, 31802.3 KiB installed

Description

PostgreSQL is a sophisticated Object-Relational DBMS, supporting almost all SQL constructs, including subselects, transactions, and user-defined types and functions. It is the most advanced open-source database available anywhere. Commercial Support is also available.

The original Postgres code was the effort of many graduate students, undergraduate students, and staff programmers working under the direction of Professor Michael Stonebraker at the University of California, Berkeley. In 1995, Andrew Yu and Jolly Chen took on the task of converting the DBMS query language to SQL and created a new database system which came to known as Postgres95. Many others contributed to the porting, testing, debugging and enhancement of the Postgres95 code. As the code improved, and 1995 faded into memory, PostgreSQL was born.

PostgreSQL development is presently being performed by a team of Internet developers who are now responsible for all current and future development. The development team coordinator is Marc G. Fournier ([email protected]). Support is available from the PostgreSQL developer/user community through the support mailing list ([email protected]).

PostgreSQL is free and the complete source is available.

In the other systems

The newest version among them is 17.12, as upstream numbers it.

SystemPortVersionVulnerabilitiesStatusMaintainerLast update
DragonFlydatabases/postgresql17-server17.11 behind since 2026-11-121 known-[email protected]-
FreeBSDdatabases/postgresql17-server17.12 newestnone known-[email protected]2026-11-12
NetBSDdatabases/postgresql17-server17.11 behind since 2026-11-12none known--2026-11-13
MidnightBSDdatabases/postgresql17-server17.11 behind since 2026-11-12no data-[email protected]2026-11-04
HardenedBSDdatabases/postgresql17-server17.11 behind since 2026-11-12no data-[email protected]-
GhostBSDdatabases/postgresql17-server17.11 behind since 2026-11-12no data-[email protected]-

Compare across BSDs

Version history 1

  1. 17.11

Upstream's version as each commit to the port's Makefile set it, or as this site first saw it in the system's packages; the tree's own revisions are not versions here.

Install

Binary package:

pkg install postgresql17-server

From DPorts:

cd /usr/dports/databases/postgresql17-server && make install clean

Dependency graph

Ports that need it on the left, what it needs to run on the right; at most 8 of each. "Dependencies" below lists them all.

Dependencies

Run dependencies 7

Configuration

No options to configure.

Service scripts
none

Message after installing

For procedural languages and postgresql functions, please note that
you might have to update them when updating the server.

If you have many tables and many clients running, consider raising
kern.maxfiles using sysctl(8), or reconfigure your kernel
appropriately.

The port is set up to use autovacuum for new databases, but you might
also want to vacuum and perhaps backup your database regularly. There
is a periodic script, /usr/local/etc/periodic/daily/502.pgsql, that
you may find useful. You can use it to backup and perform vacuum on all
databases nightly. Per default, it performs `vacuum analyze'. See the
script for instructions. For autovacuum settings, please review
~postgres/data/postgresql.conf.

If you plan to access your PostgreSQL server using ODBC, please
consider running the SQL script /usr/local/share/postgresql/odbc.sql
to get the functions required for ODBC compliance.

Please note that if you use the rc script,
/usr/local/etc/rc.d/postgresql, to initialize the database, unicode
(UTF-8) will be used to store character data by default.  Set
postgresql_initdb_flags or use login.conf settings described below to
alter this behaviour. See the start rc script for more info.

To set limits, environment stuff like locale and collation and other
things, you can set up a class in /etc/login.conf before initializing
the database. Add something similar to this to /etc/login.conf:
---
postgres:\
	:lang=en_US.UTF-8:\
	:setenv=LC_COLLATE=C:\
	:tc=default:
---
and run `cap_mkdb /etc/login.conf'.
Then add 'postgresql_login_class="postgres"' to /etc/rc.conf, or
set it as the postgres user's login class in /etc/passwd.

======================================================================

To use PostgreSQL, enable it in rc.conf using

  sysrc postgresql_enable=yes

To initialize the database, run

  service postgresql initdb

You can then start PostgreSQL by running:

  service postgresql start

For postmaster settings, see ~postgres/data/postgresql.conf

NB. FreeBSD's PostgreSQL port logs to syslog by default
    See ~postgres/data/postgresql.conf for more info

NB. If you're not using a checksumming filesystem like ZFS, you might
    wish to enable data checksumming. It can be enabled during
    the initdb phase, by adding the "--data-checksums" flag to
    the postgresql_initdb_flags rcvar. Otherwise you can enable it later by
    using pg_checksums.  Check the initdb(1) manpage for more info
    and make sure you understand the performance implications.

Known vulnerabilities 1

4 DragonFly ports depend on it, directly or through others, and may carry the vulnerable code. The ports that need it