FreshPorts -- databases/postgresql-wal2json: JSON output plugin for changeset extraction for PostgreSQL databases

Port details

postgresql-wal2json JSON output plugin for changeset extraction for PostgreSQL databases

2.5 databases =2 2.5Version of this port present on the latest quarterly branch.

Maintainer: daniel@morante.net

Port Added: 2023-08-22 08:18:18

Last Update: 2024-03-02 14:01:25

Commit Hash: 0654062

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

License: BSD3CLAUSE

WWW:

https://github.com/getsentry/wal2json/

Description:

wal2json is an output plugin for logical decoding. It means that the plugin have access to tuples produced by INSERT and UPDATE. Also, UPDATE/DELETE old row versions can be accessed depending on the configured replica identity. Changes can be consumed using the streaming protocol (logical replication slots) or by a special SQL API.

¦ ¦ ¦ ¦

Manual pages:

FreshPorts has no man page information for this port.

pkg-plist: as obtained via: make generate-plist

Expand this list (4 items)

Collapse this list.

lib/postgresql/wal2json.so
/usr/local/share/licenses/postgresql12-wal2json-2.5/catalog.mk
/usr/local/share/licenses/postgresql12-wal2json-2.5/LICENSE
/usr/local/share/licenses/postgresql12-wal2json-2.5/BSD3CLAUSE

Collapse this list.

Dependency lines:

postgresql12-wal2json>0:databases/postgresql-wal2json

To install the port:

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

To add the package, run one of these commands:

pkg install databases/postgresql-wal2json
pkg install postgresql12-wal2json

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

PKGNAME: postgresql12-wal2json

Flavors: there is no flavor information for this port.

distinfo:

TIMESTAMP = 1692687620 SHA256 (eulerto-wal2json-wal2json_2_5_GH0.tar.gz) = b516653575541cf221b99cf3f8be9b6821f6dbcfc125675c85f35090f824f00e SIZE (eulerto-wal2json-wal2json_2_5_GH0.tar.gz) = 91040

Packages (timestamps in pop-ups are UTC):

postgresql12-wal2json
ABI	aarch64	amd64	armv6	armv7	i386	powerpc	powerpc64	powerpc64le
FreeBSD:13:latest	-	-	-	-	-	-	-	-
FreeBSD:13:quarterly	-	-	-	-	-	2.5	2.5	2.5
FreeBSD:14:latest	-	-	-	-	-	-	-	-
FreeBSD:14:quarterly	-	-	-	-	-	2.5	2.5	2.5
FreeBSD:15:latest	-	-	n/a	-	n/a	2.5	2.5	2.5

postgresql13-wal2json
ABI	aarch64	amd64	armv6	armv7	i386	powerpc	powerpc64	powerpc64le
FreeBSD:13:latest	2.5	2.5	-	2.5	2.5	-	-	-
FreeBSD:13:quarterly	2.5	2.5	-	2.5	2.5	-	-	-
FreeBSD:14:latest	2.5	2.5	-	2.5	2.5	-	-	-
FreeBSD:14:quarterly	2.5	2.5	-	2.5	2.5	-	-	-
FreeBSD:15:latest	2.5	2.5	n/a	2.5	n/a	-	-	-

Dependencies

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

Build dependencies:

gmake>=4.3 : devel/gmake
postgres : databases/postgresql12-server

Runtime dependencies:

postgres : databases/postgresql12-server

There are no ports dependent upon this port

Configuration Options:

No options to configure

Options name:

databases_postgresql-wal2json

USES:

gmake pgsql:11-14

pkg-message:

For install:: You need to set up at least two parameters in postgresql.conf: wal_level = logical # # these parameters only need to set in versions 9.4, 9.5 and 9.6 # default values are ok in version 10 or later # max_replication_slots = 10 max_wal_senders = 10 After changing these parameters, a restart is needed.

Master Sites:

Expand this list (1 items)

Collapse this list.

https://codeload.github.com/eulerto/wal2json/tar.gz/wal2json_2_5?dummy=/

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: 2

Commit	Credits	Log message
Commit History - (may be incomplete: for full details, see links to repositories near top of page)
2.5 02 Mar 2024 14:01:25	Mathieu Arnold (mat)	cleanup: (ir)regular GH_TAGNAME cleanup
2.5 22 Aug 2023 08:16:26	Juraj Lutter (otis) Author: Daniel Morante	databases/postgresql-wal2json: Add new port Add postgresql-wal2json, an output plugin for logical decoding. WWW: https://github.com/eulerto/wal2json PR: 257904

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

gitlab	Jun 26
mongodb50	Jun 26
mongodb60	Jun 26
mongodb60	Jun 26
mongodb60	Jun 26
mongodb70	Jun 26
mongodb70	Jun 26
mongodb70	Jun 26
mongodb70	Jun 26
mongodb80	Jun 26
mongodb80	Jun 26
mongodb80	Jun 26
mongodb80	Jun 26
openh264	Jun 22
clamav	Jun 20

21 vulnerabilities affecting 255 ports have been reported in the past 14 days

^* - modified, not new

All vulnerabilities

Last processed:
2025-06-26 16:42:54 UTC

Ports
Home Categories Deleted ports Sanity Test Failures Newsfeeds

Statistics

Graphs
NEW Graphs (Javascript)

Calculated hourly:

Port count	33406
Broken	142
Deprecated	281
Ignore	258
Forbidden	0
Restricted	2
No CDROM	1
Vulnerable	31
Expired	15
Set to expire	223
Interactive	0
new 24 hours	2
new 48 hours	4
new 7 days	62
new fortnight	100
new month	187

Bot filter coming soon