notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
Want a good monitor light? See my photosAll times are UTC
Ukraine

Bot filter coming soon

To deter bots pegging the database CPU to 100%, a bot testing filter to be added to the website. This should not affect newsfeeds etc. Anubis seems light-weight - it''''''''s already in use within the FreeBSD Project. This notice is just a heads up in case you see something odd. This notice will be updated after Anubis is installed.

Port details
postgresql18-pgtcl TCL extension for accessing a PostgreSQL server (PGTCL-NG)
2.1.1_3 databasesnew! on this many watch lists=0 search for ports that depend on this port Find issues related to this port Report an issue related to this port View this port on Repology. pkg-fallout Package not present on quarterly.This port was created during this quarter. It will be in the next quarterly branch but not the current one.
Maintainer: ports@virtual-estates.net search for ports maintained by this maintainer
Port Added: 2025-05-08 20:04:08
Last Update: 2025-05-08 20:00:15
Commit Hash: a9608d6
Also Listed In: tcl
License: PostgreSQL
WWW:
https://sourceforge.net/projects/pgtclng/
Description:
A TCL extension for accessing PostgreSQL databases. This used to come bunlded with PostgreSQL itself, but was split into a separate project in more recent version (8+).
Homepage    cgit ¦ Codeberg ¦ GitHub ¦ GitLab ¦ SVNWeb - no subversion history for this port

Manual pages:
FreshPorts has no man page information for this port.
pkg-plist: as obtained via: make generate-plist
Expand this list (6 items)
Collapse this list.
  1. lib/pgtcl/libpgtcl2.1.1.so
  2. lib/pgtcl/pkgIndex.tcl
  3. @ldconfig
  4. /usr/local/share/licenses/pgtcl-postgresql18-2.1.1_3/catalog.mk
  5. /usr/local/share/licenses/pgtcl-postgresql18-2.1.1_3/LICENSE
  6. /usr/local/share/licenses/pgtcl-postgresql18-2.1.1_3/PostgreSQL
Collapse this list.
Dependency lines:
  • pgtcl-postgresql18>0:databases/postgresql18-pgtcl
Conflicts:
CONFLICTS:
  • pgtcl
  • pgtcl-postgresql1[012345689]
CONFLICTS_INSTALL:
  • pgtcl
  • pgtcl-postgresql[0-9][0-9]
To install the port:
cd /usr/ports/databases/postgresql18-pgtcl/ && make install clean
To add the package, run one of these commands:
  • pkg install databases/postgresql18-pgtcl
  • pkg install pgtcl-postgresql18
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.
PKGNAME: pgtcl-postgresql18
Flavors: there is no flavor information for this port.
distinfo:
TIMESTAMP = 1515323017 SHA256 (pgtcl2.1.1.tar.gz) = 1925d7cf9422f0213da725bbe245e065ab570b478881577c87ae714e18078208 SIZE (pgtcl2.1.1.tar.gz) = 196432

Expand this list (2 items)

Collapse this list.

SHA256 (pgtcldocs-20171113.zip) = af61f95881b09ae552cf33358727250e99f0f5886c0b7051d369d3a8484e549f SIZE (pgtcldocs-20171113.zip) = 164113

Collapse this list.


No package information for this port in our database
Sometimes this happens. Not all ports have packages. This is doubly so for new ports, like this one.
Master port: databases/pgtcl
Dependencies
NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
Library dependencies:
  1. libpq.so.5 : databases/postgresql18-client
  2. libtcl86.so : lang/tcl86
There are no ports dependent upon this port

Configuration Options:
===> The following configuration options are available for pgtcl-postgresql18-2.1.1_3: DOCS=on: Build and/or install documentation ===> Use 'make config' to modify these settings
Options name:
databases_postgresql18-pgtcl
USES:
pgsql:18 tcl:tea
FreshPorts was unable to extract/find any pkg message
Master Sites:
Expand this list (48 items)
Collapse this list.
  1. http://cfhcable.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  2. http://cytranet.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  3. http://deac-ams.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  4. http://deac-fra.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  5. http://deac-riga.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  6. http://downloads.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  7. http://excellmedia.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  8. http://freefr.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  9. http://gigenet.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  10. http://ixpeering.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  11. http://jaist.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  12. http://kumisystems.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  13. http://liquidtelecom.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  14. http://nchc.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  15. http://netactuate.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  16. http://netcologne.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  17. http://onboardcloud.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  18. http://phoenixnap.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  19. http://razaoinfo.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  20. http://sinalbr.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  21. http://sitsa.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  22. http://tenet.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  23. http://ufpr.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  24. http://versaweb.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  25. https://cfhcable.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  26. https://cytranet.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  27. https://deac-ams.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  28. https://deac-fra.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  29. https://deac-riga.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  30. https://downloads.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  31. https://excellmedia.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  32. https://freefr.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  33. https://gigenet.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  34. https://ixpeering.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  35. https://jaist.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  36. https://kumisystems.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  37. https://liquidtelecom.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  38. https://nchc.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  39. https://netactuate.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  40. https://netcologne.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  41. https://onboardcloud.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  42. https://phoenixnap.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  43. https://razaoinfo.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  44. https://sinalbr.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  45. https://sitsa.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  46. https://tenet.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  47. https://ufpr.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
  48. https://versaweb.dl.sourceforge.net/project/pgtclng/pgtclng/2.1.1/
Collapse this list.
Notes from UPDATING
These upgrade notes are taken from /usr/ports/UPDATING
  • 2025-05-06
    Affects: users of databases/postgresql* and other software using PostgreSQL to run
    Author: kbowling@FreeBSD.org
    Reason: 
      The default version of PostgreSQL has been switched from 16 to 17.
      The upgrade procedure can use up twice the space the databases
      currently needs. If you have a big amount of stored data take a
      closer look at the manpage of pg_upgrade for avoidance and/or
      speedup of the upgrade.
    
      The upgrade instructions consider a basic usage and do not match
      complex scenarios like replication, sharding, or similar.
    
      Upgrade instructions:
    
      First stop your PostgreSQL, create PostgreSQL-binaries and backup your data.
      If you have another Version of PostgreSQL installed, for example 16, your
      files are named according to this.
    
      # service postgresql stop
      # pkg create postgresql16-server postgresql16-contrib
      # mkdir /tmp/pg-upgrade
      # tar xf postgresql16-server-16.8.pkg -C /tmp/pg-upgrade
      # tar xf postgresql16-contrib-16.8.pkg -C /tmp/pg-upgrade
      # pkg delete -f databases/postgresql16-server databases/postgresql16-contrib databases/postgresql16-client
    
      Now update PostgreSQL:
    
        pkg user:
        # pkg install databases/postgresql17-server databases/postgresql17-contrib
        # pkg upgrade
    
        Portmaster users:
        # portmaster databases/postgresql17-server databases/postgresql17-contrib
        # portmaster -a
    
        Portupgrade users:
        # portinstall databases/postgresql17-server databases/postgresql17-contrib
        # portupgrade -a
    
      After installing the new PostgreSQL version you need to convert
      all your databases to new version:
    
      # su -l postgres -c "/usr/local/bin/initdb --encoding=utf-8 --lc-collate=C -D /var/db/postgres/data17 -U postgres"
      # su -l postgres -c "pg_upgrade -b /tmp/pg-upgrade/usr/local/bin/ -d /var/db/postgres/data16/ -B /usr/local/bin/ -D /var/db/postgres/data17/ -U postgres "
    
      Now the migration is finished. You can start PostgreSQL again with:
    
      # service postgresql start
    
      ATTENTION:
      1) If you use non-default initdb options, you have to adjust the initdb-command accordingly
    
    
Expand this list (3 items)
  • 2024-07-23
    Affects: users of databases/postgresql* and other software using PostgreSQL to run
    Author: kbowling@FreeBSD.org
    Reason: 
      The default version of PostgreSQL has been switched from 15 to 16.
      The upgrade procedure can use up twice the space the databases
      currently needs. If you have a big amount of stored data take a
      closer look at the manpage of pg_upgrade for avoidance and/or
      speedup of the upgrade.
    
      The upgrade instructions consider a basic usage and do not match
      complex scenarios like replication, sharding, or similar.
    
      Upgrade instructions:
    
      First stop your PostgreSQL, create PostgreSQL-binaries and backup your data.
      If you have another Version of PostgreSQL installed, for example 15, your
      files are named according to this.
    
      # service postgresql stop
      # pkg create postgresql15-server postgresql15-contrib
      # mkdir /tmp/pg-upgrade
      # tar xf postgresql15-server-15.7.pkg -C /tmp/pg-upgrade
      # tar xf postgresql15-contrib-15.7.pkg -C /tmp/pg-upgrade
      # pkg delete -f databases/postgresql15-server databases/postgresql15-contrib databases/postgresql15-client
    
      Now update PostgreSQL:
    
        pkg user:
        # pkg install databases/postgresql16-server databases/postgresql16-contrib
        # pkg upgrade
    
        Portmaster users:
        # portmaster databases/postgresql16-server databases/postgresql16-contrib
        # portmaster -a
    
        Portupgrade users:
        # portinstall databases/postgresql16-server databases/postgresql16-contrib
        # portupgrade -a
    
      After installing the new PostgreSQL version you need to convert
      all your databases to new version:
    
      # su -l postgres -c "/usr/local/bin/initdb --encoding=utf-8 --lc-collate=C -D /var/db/postgres/data16 -U postgres"
      # su -l postgres -c "pg_upgrade -b /tmp/pg-upgrade/usr/local/bin/ -d /var/db/postgres/data15/ -B /usr/local/bin/ -D /var/db/postgres/data16/ -U postgres "
    
      Now the migration is finished. You can start PostgreSQL again with:
    
      # service postgresql start
    
      ATTENTION:
      1) If you use non-default initdb options, you have to adjust the initdb-command accordingly
    
    
  • 2023-09-08
    Affects: users of databases/postgresql* and other software using PostgreSQL to run
    Author: kbowling@FreeBSD.org
    Reason: 
      The default version of PostgreSQL has been switched from 13 to 15.
      The upgrade procedure can use up twice the space the databases
      currently needs. If you have a big amount of stored data take a
      closer look at the manpage of pg_upgrade for avoidance and/or
      speedup of the upgrade.
    
      The upgrade instructions consider a basic usage and do not match
      complex scenarios like replication, sharding, or similar.
    
      Upgrade instructions:
    
      First stop your PostgreSQL, create PostgreSQL-binaries and backup your data.
      If you have another Version of PostgreSQL installed, for example 13, your
      files are named according to this.
    
      # service postgresql stop
      # pkg create postgresql13-server postgresql13-contrib
      # mkdir /tmp/pg-upgrade
      # tar xf postgresql13-server-13.12.pkg -C /tmp/pg-upgrade
      # tar xf postgresql13-contrib-13.12.pkg -C /tmp/pg-upgrade
      # pkg delete -f databases/postgresql13-server databases/postgresql13-contrib databases/postgresql13-client
    
      Now update PostgreSQL:
    
        pkg user:
        # pkg install databases/postgresql15-server databases/postgresql15-contrib
        # pkg upgrade
    
        Portmaster users:
        # portmaster databases/postgresql15-server databases/postgresql15-contrib
        # portmaster -a
    
        Portupgrade users:
        # portinstall databases/postgresql15-server databases/postgresql15-contrib
        # portupgrade -a
    
      After installing the new PostgreSQL version you need to convert
      all your databases to new version:
    
      # su -l postgres -c "/usr/local/bin/initdb --encoding=utf-8 --lc-collate=C -D /var/db/postgres/data15 -U postgres"
      # su -l postgres -c "pg_upgrade -b /tmp/pg-upgrade/usr/local/bin/ -d /var/db/postgres/data13/ -B /usr/local/bin/ -D /var/db/postgres/data15/ -U postgres "
    
      Now the migration is finished. You can start PostgreSQL again with:
    
      # service postgresql start
    
      ATTENTION:
      1) The default user changed from "pgsql" to "postgres" in 11. The migration steps above now assume
         the "postgres" database user and FreeBSD user.
      2) If you use non-default initdb options, you have to adjust the initdb-command accordingly
    
    
  • 2021-10-24
    Affects: users of databases/postgresql* and other software using PostgreSQL to run
    Author: kbowling@FreeBSD.org
    Reason: 
      The default version of PostgreSQL has been switched from 12 to 13.
      The upgrade procedure can use up twice the space the databases
      currently needs. If you have a big amount of stored data take a
      closer look at the manpage of pg_upgrade for avoidance and/or
      speedup of the upgrade.
    
      The upgrade instructions consider a basic usage and do not match
      complex scenarios like replication, sharding, or similar.
    
      Upgrade instructions:
    
      First stop your PostgreSQL, create PostgreSQL-binaries and backup your data.
      If you have another Version of PostgreSQL installed, for example 12.8, your
      files are named according to this.
    
      # service postgresql stop
      # pkg create postgresql12-server postgresql12-contrib
      # mkdir /tmp/pg-upgrade
      # tar xf postgresql12-server-12.8.pkg -C /tmp/pg-upgrade
      # tar xf postgresql12-contrib-12.8.pkg -C /tmp/pg-upgrade
      # pkg delete -f databases/postgresql12-server databases/postgresql12-contrib databases/postgresql12-client
    
      Now update PostgreSQL:
    
        pkg user:
        # pkg install databases/postgresql13-server databases/postgresql13-contrib
        # pkg upgrade
    
        Portmaster users:
        # portmaster databases/postgresql13-server databases/postgresql13-contrib
        # portmaster -a
    
        Portupgrade users:
        # portinstall databases/postgresql13-server databases/postgresql13-contrib
        # portupgrade -a
    
      After installing the new PostgreSQL version you need to convert
      all your databases to new version:
    
      # su -l postgres -c "/usr/local/bin/initdb --encoding=utf-8 --lc-collate=C -D /var/db/postgres/data13 -U postgres"
      # su -l postgres -c "pg_upgrade -b /tmp/pg-upgrade/usr/local/bin/ -d /var/db/postgres/data12/ -B /usr/local/bin/ -D /var/db/postgres/data13/ -U postgres "
    
      Now the migration is finished. You can start PostgreSQL again with:
    
      # service postgresql start
    
      ATTENTION:
      1) The default user changed from "pgsql" to "postgres" in 11. The migration steps above now assume
         the "postgres" database user and FreeBSD user.
      2) If you use non-default initdb options, you have to adjust the initdb-command accordingly
    
    
  • Collapse this list.

Number of commits found: 1

Commit History - (may be incomplete: for full details, see links to repositories near top of page)
This is a slave port. You may also want to view the commits to the master port: databases/pgtcl
CommitCreditsLog message
2.1.1_3
08 May 2025 20:00:15
commit hash: a9608d62ae7125d78cd9f16748f786c8581699adcommit hash: a9608d62ae7125d78cd9f16748f786c8581699adcommit hash: a9608d62ae7125d78cd9f16748f786c8581699adcommit hash: a9608d62ae7125d78cd9f16748f786c8581699ad files touched by this commit
Palle Girgensohn (girgen) search for other commits by this committer
databases/postgresql??-*: Update to latest version

PostgreSQL 17.5, 16.9, 15.13, 14.18, and 13.21 Released!

The PostgreSQL Global Development Group has released an update to all
supported versions of PostgreSQL, including 17.5, 16.9, 15.13, 14.18,
and 13.21. This release fixes 1 security vulnerability and over 60 bugs
reported over the last several months.

Security:	78b8e808-2c45-11f0-9a65-6cc21735f730
Release
notes:	https://www.postgresql.org/about/news/postgresql-175-169-1513-1418-and-1321-released-3072/

Number of commits found: 1