FreshPorts -- databases/postgresql-idn: PostgreSQL extension for libidn2

Port details

postgresql-idn PostgreSQL extension for libidn2

0.2_1 databases =2 0.2_1Version of this port present on the latest quarterly branch.

Maintainer: bofh@FreeBSD.org

Port Added: 2023-07-20 17:45:06

Last Update: 2024-05-02 13:06:58

Commit Hash: bae03bd

People watching this port, also watch:: jdictionary, py311-Automat, py311-python-gdsii, py39-PyOpenGL, p5-Sane

License: BSD3CLAUSE

WWW:

https://github.com/dyninc/postgresql-idn

Description:

At a fundamental level, this extension grants access to a number of functions provided by the libidn and libidn2 libraries. Not all of the functions provided by these libraries are exposed. Whenever possible, the code will transform the encoding of the data in the database to UTF-8 before further processing.

¦ ¦ ¦ ¦

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.

lib/postgresql/idn.so
share/postgresql/extension/idn.control
share/postgresql/extension/idn--0.2.sql
/usr/local/share/licenses/postgresql15-idn-0.2_1/catalog.mk
/usr/local/share/licenses/postgresql15-idn-0.2_1/LICENSE
/usr/local/share/licenses/postgresql15-idn-0.2_1/BSD3CLAUSE

Collapse this list.

Dependency lines:

postgresql15-idn>0:databases/postgresql-idn

To install the port:

cd /usr/ports/databases/postgresql-idn/ && make install clean

To add the package, run one of these commands:

pkg install databases/postgresql-idn
pkg install postgresql15-idn

NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.

PKGNAME: postgresql15-idn

Flavors: there is no flavor information for this port.

distinfo:

TIMESTAMP = 1689853106 SHA256 (dyninc-postgresql-idn-0.2-d4ffaec_GH0.tar.gz) = 77648e741c96ae186dcd4ce835cada228877864e390e1854c5099277337a0b06 SIZE (dyninc-postgresql-idn-0.2-d4ffaec_GH0.tar.gz) = 14784

Packages (timestamps in pop-ups are UTC):

postgresql15-idn
ABI	aarch64	amd64	armv6	armv7	i386	powerpc	powerpc64	powerpc64le
FreeBSD:13:latest	-	-	-	-	-	-	-	-
FreeBSD:13:quarterly	0.2_1	0.2_1	-	0.2_1	0.2_1	0.2	0.2	0.2
FreeBSD:14:latest	-	-	-	-	-	-	-	-
FreeBSD:14:quarterly	0.2_1	0.2_1	-	0.2_1	0.2_1	0.2	0.2	0.2
FreeBSD:15:latest	-	-	n/a	-	n/a	0.2	0.2	0.2

postgresql16-idn
ABI	aarch64	amd64	armv6	armv7	i386	powerpc	powerpc64	powerpc64le
FreeBSD:13:latest	0.2_1	0.2_1	-	0.2_1	0.2_1	-	-	-
FreeBSD:13:quarterly	-	-	-	-	-	-	-	-
FreeBSD:14:latest	0.2_1	0.2_1	-	0.2_1	0.2_1	-	-	-
FreeBSD:14:quarterly	-	-	-	-	-	-	-	-
FreeBSD:15:latest	0.2_1	0.2_1	n/a	0.2_1	n/a	-	-	-

Dependencies

NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.

Build dependencies:

gmake>=4.4.1 : devel/gmake
postgres : databases/postgresql15-server

Runtime dependencies:

postgres : databases/postgresql15-server

Library dependencies:

libidn.so : dns/libidn
libidn2.so : dns/libidn2

There are no ports dependent upon this port

Configuration Options:

No options to configure

Options name:

databases_postgresql-idn

USES:

gmake pgsql

FreshPorts was unable to extract/find any pkg message

Master Sites:

Expand this list (1 items)

Collapse this list.

https://codeload.github.com/dyninc/postgresql-idn/tar.gz/d4ffaec?dummy=/

Collapse this list.

Notes from UPDATING

These upgrade notes are taken from /usr/ports/UPDATING

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

Expand this list (2 items)

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) See the updating entry 20190829 if you are updating from a release prior to 11.
  3) 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) See the updating entry 20190829 if you are updating from a release prior to 11.
  3) If you use non-default initdb options, you have to adjust the initdb-command accordingly

Collapse this list.

Number of commits found: 2

Commit History - (may be incomplete: for full details, see links to repositories near top of page)

Commit

Credits

Log message

0.2_1
02 May 2024 13:06:58

Nuno Teixeira (eduardo)

*/*: Bump consumers of dns/libidn

Reported by:	vvd

0.2
20 Jul 2023 17:42:32

Muhammad Moinur Rahman (bofh)

databases/postgresql-idn New port

At a fundamental level, this extension grants access to a number of
functions provided by the libidn and libidn2 libraries. Not all of the
functions provided by these libraries are exposed.

Whenever possible, the code will transform the encoding of the data in
the database to UTF-8 before further processing.

WWW: https://github.com/dyninc/postgresql-idn

Sponsored by:	Bounce Commerce

Number of commits found: 2

Login
User Login Create account

Servers and bandwidth provided by
New York Internet, iXsystems, and RootBSD

This site
What is FreshPorts? About the authors Issues FAQ How big is it? Security Policy Privacy Blog Contact

Search
Enter Keywords: more...

Latest Vulnerabilities

exiv2	Sep 07
firefox	Sep 07
binutils	Sep 06
forgejo	Sep 06
forgejo7	Sep 06
firefox	Sep 05
gitea	Sep 05
openssl^*	Sep 05
openssl-quictls^*	Sep 05
openssl31^*	Sep 05
openssl31-quictls^*	Sep 05
openssl32^*	Sep 05
openssl33^*	Sep 05
qt5-webengine	Sep 05
chromium	Sep 03

16 vulnerabilities affecting 224 ports have been reported in the past 14 days

^* - modified, not new

All vulnerabilities

Last processed:
2024-09-07 14:16:01 UTC

Ports
Home Categories Deleted ports Sanity Test Failures Newsfeeds

Statistics

Graphs
NEW Graphs (Javascript)

Calculated hourly:

Port count	32728
Broken	82
Deprecated	158
Ignore	216
Forbidden	1
Restricted	2
No CDROM	1
Vulnerable	34
Expired	12
Set to expire	127
Interactive	0
new 24 hours	3
new 48 hours	8
new 7 days	48
new fortnight	70
new month	156