{"id":42632,"date":"2026-01-27T15:56:25","date_gmt":"2026-01-27T14:56:25","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=42632"},"modified":"2026-01-27T15:56:28","modified_gmt":"2026-01-27T14:56:28","slug":"commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/","title":{"rendered":"Commercial PostgreSQL distributions with TDE (1) Fujitsu Enterprise Postgres (1) Setup"},"content":{"rendered":"\n

While TDE (Transparent Data Encryption) is considered a checklist feature in some parts of the PostgreSQL community this topic comes up all over again. The same is true with our customers, it doesn’t matter at all if it technically makes sense to have TDE or not, some just must have it for reasons outside of their control, mostly due to legal requirements. As vanilla community PostgreSQL does not provide TDE the only option is to use one of the commercial distributions of PostgtreSQL. There are several out there and we’ll take a look at some of them but today we’ll start with Fujitsu Enterprise Postgres<\/a>. This will be a two blog series, the first one (this) describing how to setup this version of PostgreSQL and in the follow up post we’ll look at how TDE looks like in this distribution and how it can be setup in Fujitsu Enterprise Postgres.<\/p>\n\n\n\n

Fujitsu provides a 90 trial version for which you need to register here<\/a>. Once you’ve done that you should receive an Email with a link to download the software (around 1.3gb). The supported operating systems are either RHEL 8 & 9<\/a> or SLES 15<\/a>. If you are on Debian<\/a> or anything based on Debian such as Ubuntu<\/a> then you can already stop here as it is not supported.<\/p>\n\n\n\n

As usual, the operating system needs to be prepared, and on RHEL 9 which I am using here this means enabling the code ready builder repository and installing the required packages:<\/p>\n\n\n

\n[root@rhel9-latest ~]$ subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms\n[root@rhel9-latest ~]$ dnf install alsa-lib audit-libs bzip2-libs cyrus-sasl-lib gdb pcp-system-tools glibc glibc.i686 iputils libnsl2 libicu libgcc libmemcached-awesome libselinux libstdc++ libtool-ltdl libzstd llvm lz4-libs ncurses-libs net-tools nss-softokn-freebl pam perl-libs protobuf-c python3 rsync sudo sysstat tcl unzip xz-libs zlib perl\n<\/pre><\/div>\n\n\n
For this the system needs to be subscribed to Red Hat but you might also try either Rocky<\/a> or Alma<\/a> Linux, this should work as well (both are clones of RHEL) and those do not need a subscription.<\/p>\n\n\n\n
In the Quick Start Guide<\/a> an operating system user called “fepuser” is used, but we prefer to go with standard “postgres” user, so:<\/p>\n\n\n
\n[root@rhel9-latest ~]$ groupadd postgres\n[root@rhel9-latest ~]$ useradd -g postgres -m postgres\n[root@rhel9-latest ~]$ grep postgres \/etc\/sudoers\npostgres        ALL=(ALL)       NOPASSWD: ALL\n<\/pre><\/div>\n\n\n
We’ll also not use “\/database\/inst1” as PGDATA but rather our standard:<\/p>\n\n\n
\n[root@rhel9-latest ~]$ su - postgres\n[postgres@rhel9-latest ~]$ sudo mkdir -p \/u02\/pgdata\n[postgres@rhel9-latest ~]$ sudo chown postgres:postgres \/u02\/pgdata\/\n[postgres@rhel9-latest ~]$ exit\n<\/pre><\/div>\n\n\n
As the installation files are provided in ISO format, loop-back mount that:<\/p>\n\n\n
\n[root@rhel9-latest ~]$ mkdir \/mnt\/media\n[root@rhel9-latest ~]$ mount -t iso9660 -r -o loop \/root\/ep-postgresae-linux-x64-1800-1.iso \/mnt\/media\/\n[root@rhel9-latest ~]$ ls -l \/mnt\/media\/\ntotal 161\ndr-xr-xr-x. 4 root root  2048 Dec  4 03:24 CIR\ndr-xr-xr-x. 3 root root  2048 May 18  2023 CLIENT64\ndr-xr-xr-x. 4 root root  2048 Dec  4 03:24 COMMON\n-r-xr-xr-x. 1 root root  4847 Aug 14 10:49 install.sh\ndr-xr-xr-x. 5 root root  2048 Nov  5 08:47 manual\ndr-xr-xr-x. 2 root root 24576 Oct 29 17:04 OSS_Licence\ndr-xr-xr-x. 3 root root  2048 Jun 13  2016 parser\ndr-xr-xr-x. 3 root root  2048 Mar 27  2024 PGBACKREST\ndr-xr-xr-x. 3 root root  2048 May 18  2023 PGPOOL2\n-r--r--r--. 1 root root 46882 Nov 28 02:39 readme.txt\n-r--r--r--. 1 root root 53702 Nov 28 01:21 readme_utf8.txt\ndr-xr-xr-x. 2 root root  2048 May 18  2023 sample\ndr-xr-xr-x. 3 root root  2048 May 18  2023 SERVER\n-r-xr-xr-x. 1 root root 12848 Aug 14 10:50 silent.sh\ndr-xr-xr-x. 3 root root  2048 May 18  2023 WEBADMIN\n<\/pre><\/div>\n\n\n
That should be all to start the installation (there is a silent mode as well, but we’re not going to look into this for the scope of this post):<\/p>\n\n\n
\n[root@rhel9-latest ~]$ cd \/mnt\/media\/\n[root@rhel9-latest media]$ .\/install.sh\nERROR: The installation of Uninstall (middleware) ended abnormally.\n\nInstallation was ended abnormally.\n<\/pre><\/div>\n\n\n
… and that directly fails. Looking at the log file it becomes clear that “tar” is missing (this is a minimal installation of RHEL 9 and this does apparently does not come with tar by default):<\/p>\n\n\n
\n[root@rhel9-latest media]$ grep tar \/var\/log\/fsep_SERVER64_media_1800_install.log\nsub_envcheck.sh start\nsub_cir_install.sh start\n.\/CIR\/Linux\/cirinst.sh: line 562: tar: command not found\nsub_envcheck.sh start\nsub_cir_install.sh start\n.\/CIR\/Linux\/cirinst.sh: line 562: tar: command not found\n<\/pre><\/div>\n\n\n
So, once more:<\/p>\n\n\n
\n[root@rhel9-latest media]$ dnf install -y tar\n[root@rhel9-latest media]$ .\/install.sh\n\nThe following products can be installed:\n1: Fujitsu Enterprise Postgres Advanced Edition (64bit) 18\n2: Fujitsu Enterprise Postgres Client (64bit) 18\n3: Fujitsu Enterprise Postgres WebAdmin 18\n4: Fujitsu Enterprise Postgres Pgpool-II 18\n5: Fujitsu Enterprise Postgres pgBackRest 18\n\nSelect the product to be installed.\nNote: If installing the Server, it is strongly recommended to install WebAdmin.\nTo select multiple products, separate using commas (,). (Example: 1,2)\n[number,all,q](The default value is 1,2,3): all\n<\/pre><\/div>\n\n\n
From the output above we can see that Fujitsu bundles Pgpool-II<\/a> and pgBackRest<\/a> with their distribution of PostgreSQL. We’re just going to install “all” and the installation runs smoothly until the end:<\/p>\n\n\n
\nSelected product\n  Fujitsu Enterprise Postgres Advanced Edition (64bit) 18\n  Fujitsu Enterprise Postgres Client (64bit) 18\n  Fujitsu Enterprise Postgres WebAdmin 18\n  Fujitsu Enterprise Postgres Pgpool-II 18\n  Fujitsu Enterprise Postgres pgBackRest 18\n\nDo you want to install the above product?\ny: Proceed to the next step\nn: Select the product again\nq: Quit without installing\n[y,n,q](The default value is y): y\n\n==============================================================================\n\nProduct to be installed\n  Fujitsu Enterprise Postgres Advanced Edition (64bit) 18\n    New installation\n  Fujitsu Enterprise Postgres Client (64bit) 18\n    New installation\n  Fujitsu Enterprise Postgres WebAdmin 18\n    New installation\n  Fujitsu Enterprise Postgres Pgpool-II 18\n    New installation\n  Fujitsu Enterprise Postgres pgBackRest 18\n    New installation\n\nInstallation directory information\n  Fujitsu Enterprise Postgres Advanced Edition (64bit) 18\n    \/opt\/fsepv18server64\n  Fujitsu Enterprise Postgres Client (64bit) 18\n    \/opt\/fsepv18client64\n  Fujitsu Enterprise Postgres WebAdmin 18\n    \/opt\/fsepv18webadmin\n  Fujitsu Enterprise Postgres Pgpool-II 18\n    \/opt\/fsepv18pgpool-II\n  Fujitsu Enterprise Postgres pgBackRest 18\n    \/opt\/fsepv18pgbackrest\n\nSetup information\n  WebAdmin setup: Execute\n  Web server port number: 27515\n  WebAdmin internal port number: 27516\n\nStart installation using the above information?\ny: Start the installation\nc: Change the information\nq: Quit without installing\n[y,c,q](The default value is y): y\n\n\n==============================================================================\nStarting installation.\n\nFujitsu Enterprise Postgres Advanced Edition (64bit) 18 Installation\n\nInstallation is complete.\n\nFujitsu Enterprise Postgres Client (64bit) 18 Installation\n\nInstallation is complete.\n\nFujitsu Enterprise Postgres WebAdmin 18 Installation\n\nInstallation is complete.\n\nFujitsu Enterprise Postgres Pgpool-II 18 Installation\n\nInstallation is complete.\n\nFujitsu Enterprise Postgres pgBackRest 18 Installation\n\nInstallation is complete.\n\nStarting setup.\n\nSets up WebAdmin.\n\nSetup is complete.\n\nInstalled successfully.\n<\/pre><\/div>\n\n\n
All the files have been installed under “\/opt”, grouped by component:<\/p>\n\n\n
\n[root@rhel9-latest ~]$ ls -l \/opt\/\ntotal 4\ndr-xr-x---.  5 root root   59 Jan 26 09:41 FJSVcir\ndrwxr-xr-x.  3 root root 4096 Jan 26 09:42 FJSVqstl\ndrwxr-xr-x. 14 root root  155 Nov 21 08:57 fsepv18client64\ndrwxr-xr-x.  7 root root   63 Jan 26 09:42 fsepv18pgbackrest\ndrwxr-xr-x.  9 root root   91 Jan 26 09:42 fsepv18pgpool-II\ndrwxr-xr-x. 15 root root  162 Oct 27 05:57 fsepv18server64\ndrwxr-xr-x. 13 root root  137 Jan 26 09:42 fsepv18webadmin\n<\/pre><\/div>\n\n\n
What follows below is the installation of our DMK<\/a>, just ignore it (or ask in the comments if you’re interested), this makes it a bit easier with the environment:<\/p>\n\n\n
\n[postgres@rhel9-latest ~]$ sudo mkdir -p \/opt\/local\n[postgres@rhel9-latest ~]$ sudo chown postgres:postgres \/opt\/local\/\n[postgres@rhel9-latest ~]$ cd \/opt\/local\/\n[postgres@rhel9-latest local]$ unzip \/home\/postgres\/dmk_postgres-2.4.1.zip\n[postgres@rhel9-latest local]$ cat \/etc\/pgtab\nfe18:\/opt\/fsepv18server64\/bin\/:dummy:9999:D\n[postgres@rhel9-latest local]$ sudo chown postgres:postgres \/etc\/pgtab\n[postgres@rhel9-latest local]$ cp dmk\/etc\/dmk.conf.unix dmk\/etc\/dmk.conf\n[postgres@rhel9-latest local]$ dmk\/bin\/dmk.bash\n[postgres@rhel9-latest local]$ cat dmk\/templates\/profile\/dmk.postgres.profile >> ~\/.bash_profile\n[postgres@rhel9-latest local]$ exit\nlogout\n[root@rhel9-latest ~]$ su - postgres\nLast login: Mon Jan 26 09:51:49 CET 2026 from 192.168.122.1 on pts\/1\n\n\n PostgreSQL Clusters up and running on this host:\n ----------------------------------------------------------------------------------------------\n\n PostgreSQL Clusters NOT running on this host:\n ----------------------------------------------------------------------------------------------\n<\/pre><\/div>\n\n\n
Having that setup we do not need to worry about PATH and other environment settings, they just got setup correctly, so we can directly ask for which version of PostgreSQL we’re faced here:<\/p>\n\n\n
\npostgres@rhel9-latest:\/home\/postgres\/ [fe18] which initdb\n\/opt\/fsepv18server64\/bin\/initdb\npostgres@rhel9-latest:\/home\/postgres\/ [fe18] initdb --version\ninitdb (PostgreSQL) 18.0\n<\/pre><\/div>\n\n\n
Except for the installation directory there does not seem to be a special Fujitsu branding and we’re on PostgreSQL 18.0. The preferred method of creating a new PostgreSQL instance seems to be to use WebAdmin<\/a> which was installed and started during the installation:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
We could go this way, but as we do want to know how it looks in the background we’re going to use plain initdb<\/a>. Looking at the switches of this version of initdb it is mostly the same as plain PostgreSQL except for the “coordinator”, “coord_conninfo”, and “datanode” switches:<\/p>\n\n\n
\npostgres@rhel9-latest:\/home\/postgres\/ [fe18] initdb --help\ninitdb initializes a PostgreSQL database cluster.\n\nUsage:\n  initdb [OPTION]... [DATADIR]\n\nOptions:\n  -A, --auth=METHOD         default authentication method for local connections\n      --auth-host=METHOD    default authentication method for local TCP\/IP connections\n      --auth-local=METHOD   default authentication method for local-socket connections\n      --coordinator         create an instance of the coordinator       <- XXXXXXXXXXXXXXXXXXXXXXXXX\n      --coord_conninfo      connection parameters to the coordinator    <- XXXXXXXXXXXXXXXXXXXXXXXXX\n      --datanode            create an instance of the datanode          <- XXXXXXXXXXXXXXXXXXXXXXXXX\n [-D, --pgdata=]DATADIR     location for this database cluster\n  -E, --encoding=ENCODING   set default encoding for new databases\n  -g, --allow-group-access  allow group read\/execute on data directory\n      --icu-locale=LOCALE   set ICU locale ID for new databases\n      --icu-rules=RULES     set additional ICU collation rules for new databases\n  -k, --data-checksums      use data page checksums\n      --locale=LOCALE       set default locale for new databases\n      --lc-collate=, --lc-ctype=, --lc-messages=LOCALE\n      --lc-monetary=, --lc-numeric=, --lc-time=LOCALE\n                            set default locale in the respective category for\n                            new databases (default taken from environment)\n      --no-locale           equivalent to --locale=C\n      --builtin-locale=LOCALE\n                            set builtin locale name for new databases\n      --locale-provider={builtin|libc|icu}\n                            set default locale provider for new databases\n      --no-data-checksums   do not use data page checksums\n      --pwfile=FILE         read password for the new superuser from file\n  -T, --text-search-config=CFG\n                            default text search configuration\n  -U, --username=NAME       database superuser name\n  -W, --pwprompt            prompt for a password for the new superuser\n  -X, --waldir=WALDIR       location for the write-ahead log directory\n      --wal-segsize=SIZE    size of WAL segments, in megabytes\n\nLess commonly used options:\n  -c, --set NAME=VALUE      override default setting for server parameter\n  -d, --debug               generate lots of debugging output\n      --discard-caches      set debug_discard_caches=1\n  -L DIRECTORY              where to find the input files\n  -n, --no-clean            do not clean up after errors\n  -N, --no-sync             do not wait for changes to be written safely to disk\n      --no-sync-data-files  do not sync files within database directories\n      --no-instructions     do not print instructions for next steps\n  -s, --show                show internal settings, then exit\n      --sync-method=METHOD  set method for syncing files to disk\n  -S, --sync-only           only sync database files to disk, then exit\n\nOther options:\n  -V, --version             output version information, then exit\n  -?, --help                show this help, then exit\n\nIf the data directory is not specified, the environment variable PGDATA\nis used.\n\nReport bugs to <pgsql-bugs@lists.postgresql.org>.\nPostgreSQL home page: <https:\/\/www.postgresql.org\/>\n<\/pre><\/div>\n\n\n
(Not sure if bugs for this version of initdb really should go to the official mailing lists, but this is another topic).<\/p>\n\n\n\n
Initializing a new instance is not different from what we know from vanilla PostgreSQL:<\/p>\n\n\n
\npostgres@rhel9-latest:\/home\/postgres\/ [fe18] initdb --pgdata=\/u02\/pgdata\/fe18\/PG1 --lc-collate="C" --lc-ctype="C" --encoding=UTF8\nThe files belonging to this database system will be owned by user "postgres".\nThis user must also own the server process.\n\nThe database cluster will be initialized with this locale configuration:\n  locale provider:   libc\n  LC_COLLATE:  C\n  LC_CTYPE:    C\n  LC_MESSAGES: en_US.UTF-8\n  LC_MONETARY: en_US.UTF-8\n  LC_NUMERIC:  en_US.UTF-8\n  LC_TIME:     en_US.UTF-8\nThe default text search configuration will be set to "english".\n\nData page checksums are enabled.\n\ncreating directory \/u02\/pgdata\/fe18\/PG1 ... ok\ncreating subdirectories ... ok\nselecting dynamic shared memory implementation ... posix\nselecting default "max_connections" ... 100\nselecting default "shared_buffers" ... 128MB\nselecting default time zone ... Europe\/Berlin\ncreating configuration files ... ok\nrunning bootstrap script ... ok\nperforming post-bootstrap initialization ... ok\nsyncing data to disk ... ok\n\ninitdb: warning: enabling "trust" authentication for local connections\ninitdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.\n\nSuccess. You can now start the database server using:\n\n    pg_ctl -D \/u02\/pgdata\/fe18\/PG1 -l logfile start\n<\/pre><\/div>\n\n\n
As we do want the instance to start automatically when the operating system is starting up lets use the systemd service template provided by Fujitsu to integrate that with systemd:<\/p>\n\n\n
\n## Template\npostgres@rhel9-latest:\/home\/postgres\/ [fe18] cat \/opt\/fsepv18server64\/share\/fsepsvoi.service.sample\n# Copyright FUJITSU LIMITED 2025\n[Unit]\nDescription=FUJITSU Enterprise Postgres <inst1>\nRequires=network-online.target\nAfter=network.target network-online.target\n\n[Service]\nExecStart=\/bin\/bash -c '\/opt\/fsepv<x>server64\/bin\/pgx_symstd start \/opt\/fsepv<x>server64 \/database\/inst1'\nExecStop=\/bin\/bash -c '\/opt\/fsepv<x>server64\/bin\/pgx_symstd stop \/opt\/fsepv<x>server64 \/database\/inst1'\nExecReload=\/bin\/bash -c '\/opt\/fsepv<x>server64\/bin\/pgx_symstd reload \/opt\/fsepv<x>server64 \/database\/inst1'\nType=forking\nUser=fsepuser\nGroup=fsepuser\n\n[Install]\nWantedBy=multi-user.target\n\n## Adapted\npostgres@rhel9-latest:\/home\/postgres\/ [fe18] sudo cat \/etc\/systemd\/system\/fe-postgres-1.service\n# Copyright FUJITSU LIMITED 2025\n[Unit]\nDescription=FUJITSU Enterprise Postgres PG1\nRequires=network-online.target\nAfter=network.target network-online.target\n\n[Service]\nEnvironment="PATH=\/opt\/fsepv18server64\/bin\/:$PATH"\nExecStart=\/bin\/bash -c '\/opt\/fsepv18server64\/bin\/pgx_symstd start \/opt\/fsepv18server64 \/u02\/pgdata\/fe18\/PG1\/'\nExecStop=\/bin\/bash -c '\/opt\/fsepv18server64\/bin\/pgx_symstd stop \/opt\/fsepv18server64 \/u02\/pgdata\/fe18\/PG1\/'\nExecReload=\/bin\/bash -c '\/opt\/fsepv18server64\/bin\/pgx_symstd reload \/opt\/fsepv18server64 \/u02\/pgdata\/fe18\/PG1\/'\nType=forking\nUser=postgres\nGroup=postgres\n\n[Install]\nWantedBy=multi-user.target\n<\/pre><\/div>\n\n\n
“pgx_symstd” is a simple wrapper around pg_ctl<\/a>, not sure about the reason for this. Enable and start:<\/p>\n\n\n
\npostgres@rhel9-latest:\/home\/postgres\/ [fe18] sudo systemctl enable fe-postgres-1\nCreated symlink \/etc\/systemd\/system\/multi-user.target.wants\/fe-postgres-1.service \u2192 \/etc\/systemd\/system\/fe-postgres-1.service.\n11:22:11 postgres@rhel9-latest:\/home\/postgres\/ [fe18] sudo systemctl daemon-reload\n11:22:13 postgres@rhel9-latest:\/home\/postgres\/ [fe18] sudo systemctl start fe-postgres-1\n11:22:20 postgres@rhel9-latest:\/home\/postgres\/ [fe18] sudo systemctl status fe-postgres-1\n\u25cf fe-postgres-1.service - FUJITSU Enterprise Postgres PG1\n     Loaded: loaded (\/etc\/systemd\/system\/fe-postgres-1.service; enabled; preset: disabled)\n     Active: active (running) since Mon 2026-01-26 11:22:16 CET; 8s ago\n    Process: 33363 ExecStart=\/bin\/bash -c \/opt\/fsepv18server64\/bin\/pgx_symstd start \/opt\/fsepv18server64 \/u02\/pgdata\/fe18\/PG1\/ (code=exited, status=0\/SUCCESS)\n   Main PID: 33366 (postgres)\n      Tasks: 10 (limit: 7834)\n     Memory: 31.3M (peak: 33.0M)\n        CPU: 48ms\n     CGroup: \/system.slice\/fe-postgres-1.service\n             \u251c\u250033366 \/opt\/fsepv18server64\/bin\/postgres -D \/u02\/pgdata\/fe18\/PG1\n             \u251c\u250033367 "postgres: io worker 0"\n             \u251c\u250033368 "postgres: io worker 1"\n             \u251c\u250033369 "postgres: io worker 2"\n             \u251c\u250033370 "postgres: checkpointer "\n             \u251c\u250033371 "postgres: background writer "\n             \u251c\u250033373 "postgres: walwriter "\n             \u251c\u250033374 "postgres: autovacuum launcher "\n             \u251c\u250033375 "postgres: user profile status writer "\n             \u2514\u250033376 "postgres: logical replication launcher "\n\nJan 26 11:22:16 rhel9-latest bash[33366]: 2026-01-26 10:22:16.003 GMT [33366] WARNING:  The license will expire in 90 days.\nJan 26 11:22:16 rhel9-latest bash[33366]: 2026-01-26 11:22:16.014 CET [33366] LOG:  starting PostgreSQL 18.0 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 11.3.1 20221121 (Red Hat 11.3.1-4), 64-bit\nJan 26 11:22:16 rhel9-latest bash[33366]: 2026-01-26 11:22:16.015 CET [33366] LOG:  listening on IPv6 address "::1", port 27500\nJan 26 11:22:16 rhel9-latest bash[33366]: 2026-01-26 11:22:16.015 CET [33366] LOG:  listening on IPv4 address "127.0.0.1", port 27500\nJan 26 11:22:16 rhel9-latest bash[33366]: 2026-01-26 11:22:16.019 CET [33366] LOG:  listening on Unix socket "\/tmp\/.s.PGSQL.27500"\n<\/pre><\/div>\n\n\n
Notice the license warning in the output. Another thing to note is the “user profile status writer” process as this does not exist in community PostgreSQL. Looking at the version of PostgreSQL confirms that we’re on 18.0:<\/p>\n\n\n
\npostgres@rhel9-latest:\/home\/postgres\/ [fe18] psql\npsql (18.0)\nType "help" for help.\n\npostgres=$ select version();\n                                                 version\n----------------------------------------------------------------------------------------------------------\n PostgreSQL 18.0 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 11.3.1 20221121 (Red Hat 11.3.1-4), 64-bit\n(1 row)\n\npostgres=$\n<\/pre><\/div>\n\n\n
There is also a file provided by Fujitsu which details the version installed:<\/p>\n\n\n
\npostgres@rhel9-latest:\/home\/postgres\/ [fe18] cat \/opt\/fsepv18server64\/etc\/product.inf\nPRODUCT="Fujitsu Enterprise Postgres Advanced Edition"\nMAJOR=18\nMINOR=0\nMICRO=0\nVERSION1="18"\nVERSION2=1800\nRELEASE=0\nEDITION=AE\nEXEMODE=64\nTYPE=SERVER\nAREA=COMMON\nOSTYPE=Linux\nPRODUCTTYPE=FSEP\nSOFTWAREID=7A705C507E0E11EE8008303035303536\nFJQSSNAME="FSEP1864"\nPKG_MC=ON\nFORMALNAME="Fujitsu Enterprise Postgres"\n<\/pre><\/div>\n\n\n
Finally, let’s import the new instance into WebAdmin:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Reducing<\/p>\n\n\n\n
Importing works fine, but there are not a lot of parameters which can be changed in WebAdmin, maybe this is on purpose.<\/p>\n\n\n\n
Final thoughts about the installation and initial setup of the instance:<\/p>\n\n\n\n
    \n
  • Bundling several products makes sense, as you anyway need a tool for backup\/restore and connection pooling. I am not judging the selection of the tools.<\/li>\n\n\n\n
  • Providing a graphical user interface makes sense for users not very familiar with PostgreSQL but I guess more experienced users will not use it.<\/li>\n\n\n\n
  • There is no Fujitsu branding (at least not in the binaries).<\/li>\n\n\n\n
  • The installation process is easy and straight forward.<\/li>\n\n\n\n
  • Not sure about the pgx_ wrappers, at least for the systemd integration this seems not to be necessary (there are several more of them we’ve not looked at right now).<\/li>\n\n\n\n
  • Limiting the supported operating systems to Red Hat and SUSE excludes the complete Debian world. I guess this is because Fujitsu is targeting larger customers which are anyway on either Red Hat or SUSE. <\/li>\n<\/ul>\n\n\n\n
    In the next post we’ll look at how TDE looks like in Fujitsu Enterprise Postgres.<\/p>\n","protected":false},"excerpt":{"rendered":"
    While TDE (Transparent Data Encryption) is considered a checklist feature in some parts of the PostgreSQL community this topic comes up all over again. The same is true with our customers, it doesn’t matter at all if it technically makes sense to have TDE or not, some just must have it for reasons outside of […]<\/p>\n","protected":false},"author":29,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229,198],"tags":[77],"type_dbi":[],"class_list":["post-42632","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","category-database-management","tag-postgresql"],"acf":[],"yoast_head":"\nCommercial PostgreSQL distributions with TDE (1) Fujitsu Enterprise Postgres (1) Setup - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Commercial PostgreSQL distributions with TDE (1) Fujitsu Enterprise Postgres (1) Setup\" \/>\n<meta property=\"og:description\" content=\"While TDE (Transparent Data Encryption) is considered a checklist feature in some parts of the PostgreSQL community this topic comes up all over again. The same is true with our customers, it doesn’t matter at all if it technically makes sense to have TDE or not, some just must have it for reasons outside of […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-01-27T14:56:25+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-01-27T14:56:28+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/01\/f1.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1459\" \/>\n\t<meta property=\"og:image:height\" content=\"671\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Daniel Westermann\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@westermanndanie\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Daniel Westermann\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/\"},\"author\":{\"name\":\"Daniel Westermann\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"headline\":\"Commercial PostgreSQL distributions with TDE (1) Fujitsu Enterprise Postgres (1) Setup\",\"datePublished\":\"2026-01-27T14:56:25+00:00\",\"dateModified\":\"2026-01-27T14:56:28+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/\"},\"wordCount\":941,\"commentCount\":0,\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/01\/f1-1024x471.png\",\"keywords\":[\"PostgreSQL\"],\"articleSection\":[\"Database Administration & Monitoring\",\"Database management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/\",\"name\":\"Commercial PostgreSQL distributions with TDE (1) Fujitsu Enterprise Postgres (1) Setup - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/01\/f1-1024x471.png\",\"datePublished\":\"2026-01-27T14:56:25+00:00\",\"dateModified\":\"2026-01-27T14:56:28+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/#primaryimage\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/01\/f1.png\",\"contentUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/01\/f1.png\",\"width\":1459,\"height\":671},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Commercial PostgreSQL distributions with TDE (1) Fujitsu Enterprise Postgres (1) Setup\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66\",\"name\":\"Daniel Westermann\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g\",\"caption\":\"Daniel Westermann\"},\"description\":\"Daniel Westermann is Principal Consultant and Technology Leader Open Infrastructure at dbi services. He has more than 15 years of experience in management, engineering and optimization of databases and infrastructures, especially on Oracle and PostgreSQL. Since the beginning of his career, he has specialized in Oracle Technologies and is Oracle Certified Professional 12c and Oracle Certified Expert RAC\/GridInfra. Over time, Daniel has become increasingly interested in open source technologies, becoming \u201cTechnology Leader Open Infrastructure\u201d and PostgreSQL expert. \u00a0Based on community or EnterpriseDB tools, he develops and installs complex high available solutions with PostgreSQL. He is also a certified PostgreSQL Plus 9.0 Professional and a Postgres Advanced Server 9.4 Professional. He is a regular speaker at PostgreSQL conferences in Switzerland and Europe. Today Daniel is also supporting our customers on AWS services such as AWS RDS, database migrations into the cloud, EC2 and automated infrastructure management with AWS SSM (System Manager). He is a certified AWS Solutions Architect Professional. Prior to dbi services, Daniel was Management System Engineer at LC SYSTEMS-Engineering AG in Basel. Before that, he worked as Oracle Developper &\u00a0Project Manager at Delta Energy Solutions AG in Basel (today Powel AG). Daniel holds a diploma in Business Informatics (DHBW, Germany). His branch-related experience mainly covers the pharma industry, the financial sector, energy, lottery and telecommunications.\",\"sameAs\":[\"https:\/\/x.com\/westermanndanie\"],\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/daniel-westermann\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Commercial PostgreSQL distributions with TDE (1) Fujitsu Enterprise Postgres (1) Setup - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/","og_locale":"en_US","og_type":"article","og_title":"Commercial PostgreSQL distributions with TDE (1) Fujitsu Enterprise Postgres (1) Setup","og_description":"While TDE (Transparent Data Encryption) is considered a checklist feature in some parts of the PostgreSQL community this topic comes up all over again. The same is true with our customers, it doesn’t matter at all if it technically makes sense to have TDE or not, some just must have it for reasons outside of […]","og_url":"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/","og_site_name":"dbi Blog","article_published_time":"2026-01-27T14:56:25+00:00","article_modified_time":"2026-01-27T14:56:28+00:00","og_image":[{"width":1459,"height":671,"url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/01\/f1.png","type":"image\/png"}],"author":"Daniel Westermann","twitter_card":"summary_large_image","twitter_creator":"@westermanndanie","twitter_misc":{"Written by":"Daniel Westermann","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/"},"author":{"name":"Daniel Westermann","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"headline":"Commercial PostgreSQL distributions with TDE (1) Fujitsu Enterprise Postgres (1) Setup","datePublished":"2026-01-27T14:56:25+00:00","dateModified":"2026-01-27T14:56:28+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/"},"wordCount":941,"commentCount":0,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/01\/f1-1024x471.png","keywords":["PostgreSQL"],"articleSection":["Database Administration & Monitoring","Database management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/","url":"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/","name":"Commercial PostgreSQL distributions with TDE (1) Fujitsu Enterprise Postgres (1) Setup - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/01\/f1-1024x471.png","datePublished":"2026-01-27T14:56:25+00:00","dateModified":"2026-01-27T14:56:28+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/01\/f1.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2026\/01\/f1.png","width":1459,"height":671},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/commercial-postgresql-distributions-with-tde-1-fujitsu-enterprise-postgres-1-setup\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Commercial PostgreSQL distributions with TDE (1) Fujitsu Enterprise Postgres (1) Setup"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8d08e9bd996a89bd75c0286cbabf3c66","name":"Daniel Westermann","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/31350ceeecb1dd8986339a29bf040d4cd3cd087d410deccd8f55234466d6c317?s=96&d=mm&r=g","caption":"Daniel Westermann"},"description":"Daniel Westermann is Principal Consultant and Technology Leader Open Infrastructure at dbi services. He has more than 15 years of experience in management, engineering and optimization of databases and infrastructures, especially on Oracle and PostgreSQL. Since the beginning of his career, he has specialized in Oracle Technologies and is Oracle Certified Professional 12c and Oracle Certified Expert RAC\/GridInfra. Over time, Daniel has become increasingly interested in open source technologies, becoming \u201cTechnology Leader Open Infrastructure\u201d and PostgreSQL expert. \u00a0Based on community or EnterpriseDB tools, he develops and installs complex high available solutions with PostgreSQL. He is also a certified PostgreSQL Plus 9.0 Professional and a Postgres Advanced Server 9.4 Professional. He is a regular speaker at PostgreSQL conferences in Switzerland and Europe. Today Daniel is also supporting our customers on AWS services such as AWS RDS, database migrations into the cloud, EC2 and automated infrastructure management with AWS SSM (System Manager). He is a certified AWS Solutions Architect Professional. Prior to dbi services, Daniel was Management System Engineer at LC SYSTEMS-Engineering AG in Basel. Before that, he worked as Oracle Developper &\u00a0Project Manager at Delta Energy Solutions AG in Basel (today Powel AG). Daniel holds a diploma in Business Informatics (DHBW, Germany). His branch-related experience mainly covers the pharma industry, the financial sector, energy, lottery and telecommunications.","sameAs":["https:\/\/x.com\/westermanndanie"],"url":"https:\/\/www.dbi-services.com\/blog\/author\/daniel-westermann\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/42632","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/29"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=42632"}],"version-history":[{"count":17,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/42632\/revisions"}],"predecessor-version":[{"id":42660,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/42632\/revisions\/42660"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=42632"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=42632"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=42632"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=42632"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}