Add wal2json package

[paraddise]

I need wal2json in my application, with default image cloudnative-pg/postgresql:16.2 I get folowwing error in my application

Original Error: *pgconn.PgError ERROR: could not access file "wal2json": No such file or directory (SQLSTATE 58P01)

[dosubot[bot]]

Hi, @paraddise. I'm Dosu, and I'm helping the postgres-containers team manage their backlog. I'm marking this issue as stale.

Issue Summary

• You requested the inclusion of the wal2json package in the cloudnative-pg/postgresql:16.2 image.
• Your application requires this package to function correctly, and currently encounters an error due to its absence.
• There have been no further comments or developments on this issue.

Next Steps

• Please let me know if this issue is still relevant to the latest version of the postgres-containers repository by commenting here.
• If there is no further activity, this issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!

[paraddise]

Steel relevant, I'm waiting for PR review https://github.com/cloudnative-pg/postgres-containers/pull/105

[dosubot[bot]]

@ sxd, the user @paraddise has indicated that the issue regarding the inclusion of the wal2json package is still relevant and they are waiting for a PR review (see #105). Could you please assist them with this?

[reyvonger]

bump

[ardentperf]

Hey, sorry this fell through the cracks without a response for so long. I think the underlying question is "what does standard image mean"?

In #132 which introduced the minimal and standard images, we actually also proposed a third image type full - but we haven't yet built that one. And it might still need some more thought.

I think a legitimate concern is that we don't want the standard to get bloated, and if we're not careful then i do worry it easily could grow until it eventually includes almost all the extensions already packaged for debian. Another related development is the new Postgres 18 feature which may allow us to package extensions as read-only image volumes mounted to the container.

Another thing I wonder about... standard includes all the OS glibc locales by default, but I think nudging people toward ICU by default would be a better choice.

Anyway - in the meantime it's not hard to create your own images based on the CNPG minimal image and add the extensions you need. I think this is a reasonable approach in the short term, because we really want to make sure the path forward for official CNPG images is carefully thought out.