public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Miroslav Šulc (fordfrog)" <fordfrog@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Patrick Lauer <patrick@gentoo.org>
Subject: Re: [gentoo-dev] RFC: New PostgreSQL categories
Date: Mon, 28 Oct 2024 14:57:09 +0100	[thread overview]
Message-ID: <1c00d0e4f449e078ecd7d6ae2e7111d6@gentoo.org> (raw)
In-Reply-To: <7eb6a37e-bd6a-434b-b97a-21eacdbed981@gentoo.org>

just a sidenote, dev-db/apgdiff is also a tool specific to postgresql (i 
authored it long time ago).

Dne 2024-10-28 14:49, Patrick Lauer napsal:
> Hello everyone,
> 
> I've just returned from the pgconf.eu conference, and this has 
> motivated me to try to improve the packaging situation for all things 
> PostgreSQL in Gentoo.
> 
> Right now everything just goes into dev-db/ category. That's not 
> inherently wrong, but it feels a bit overloaded to me. So I'd like to 
> add two new categories. I'm relatively indifferent about the naming, 
> good suggestions welcome, but locally I ended up naming them "pg-tools" 
> and "pg-extensions". As the name suggests, one category is tools around 
> PostgreSQL, and the other is extensions. (Or maybe it makes sense to 
> put all of it into a dev-postgres category?)
> 
> A good amount of things are in-tree already, a lot of other things I've 
> accumulated in a local repository. Most of it is very boring (i.e. most 
> extensions 'just' use a plain Makefile) and has low rate of change.
> 
> The packages involved are:
> 
> - extensions, in-tree:
> dev-db/plr
> dev-db/pgrouting
> dev-db/citus
> dev-db/pgtap
> dev-db/postgis
> dev-db/slony1
> dev-db/pglogical
> dev-db/timescaledb
> 
> - extensions, new packages:
> pg-extensions/clickhouse_fdw  | Clickhouse ForeignDataWrapper for 
> PostgreSQL
> pg-extensions/icu_ext  | An extension to expose functionality from ICU 
> to PostgreSQL applications.
> pg-extensions/lantern  | Vector similarity search for Postgresql
> pg-extensions/mongo_fdw  | MongoDB foreign data wrapper for Postgresql
> pg-extensions/mysql_fdw  | MySQL/MariaDB foreign data wrapper for 
> Postgresql
> pg-extensions/odbc_fdw  | ODBC FDW for PostgreSQL
> pg-extensions/pg_auto_failover  | Monitors and manage automated 
> failover for Postgres clusters
> pg-extensions/pg_crash  | Reliably crash PostgreSQL
> pg-extensions/pg_cron  | simple cron-based job scheduler for PostgreSQL
> pg-extensions/pg_embedding  | Hierarchical Navigable Small World (HNSW) 
> for vector similarity search
> pg-extensions/pg_failover_slots  | Failover for replication slots
> pg-extensions/pg_globalxact  | tools for distributed transactions 
> within PostgreSQL
> pg-extensions/pg_hint_plan  | tweak PostgreSQL execution plans with 
> hints
> pg-extensions/pg_ivm  | Incremental View Maintenance for PostgreSQL
> pg-extensions/pg_jobmon  | Autonomous logging capabilities for 
> PostgreSQL transactions/functions
> pg-extensions/pg_partman  | PostgreSQL Partition Manager
> pg-extensions/pg_profile  | find the most resource intensive activities 
> in PostgreSQL
> pg-extensions/pg_qualstats  | statistics on predicates found in WHERE 
> statements and JOIN clauses
> pg-extensions/pg_stat_kcache  | Gathers statistics about real reads and 
> writes done by the filesystem layer
> pg-extensions/pg_wait_sampling  | sampling based statistics of wait 
> events in PostgreSQL
> pg-extensions/pgfaceting  | Vector similarity search for Postgresql
> pg-extensions/pgroonga  | Fast FullTextSearch for PostgreSQL
> pg-extensions/pgsphere  | PostgreSQL extension for spherical geometry
> pg-extensions/pgsql-ogr-fdw  | OGR FDW for PostgreSQL
> pg-extensions/pgvector  | Vector similarity search for Postgresql
> pg-extensions/pgvectorscale | enhanced ML/vector extension
> pg-extensions/pllua  | Embeds Lua into PostgreSQL as a procedural 
> language module.
> pg-extensions/postgres-tde-ext  | experimental encrypted access method
> pg-extensions/postgresql-unit  | SI Units for PostgreSQL
> pg-extensions/rum  | RUM access method
> pg-extensions/tds_fdw  | TabularDataStream foreign data wrapper
> 
> The tools are:
> - in tree:
> dev-db/barman
> dev-db/pg_top
> dev-db/pgagent
> dev-db/pgbouncer
> dev-db/pgcli
> dev-db/pgmodeler
> dev-db/pgpool2
> dev-db/pgxnclient
> dev-db/phppgadmin
> dev-db/pspg
> dev-db/psqlodbc
> dev-db/repmgr
> dev-db/slony1
> 
> - new packages:
> pg-tools/patroni  | PostgreSQL HA with ZooKeeper, etcd or Consul
> pg-tools/pg_catcheck  | Postgres system catalog check tool
> pg-tools/pg_checksums_ext  | Postgres data checksum tool
> pg-tools/pg_timetable  | Advanced scheduling for PostgreSQL
> pg-tools/pgbackrest  | Simple, reliable, scalable backup solution to 
> postgres
> pg-tools/pgcopydb  | Postgres DB copy tool
> pg-tools/pgloader  | loads data into PostgreSQL
> pg-tools/pgroll  | Zero-downtime, reversible, schema migrations for 
> Postgres
> pg-tools/sqlpage  | A SQL-only web application framework. Takes .sql 
> files and formats the query result using pre-made configurable 
> professional-looking components.
> pg-tools/vip-manager  | Manages a virtual IP based on state kept in 
> etcd or Consul
> pg-tools/wal-g  | archival restoration tool for PostgreSQL, 
> MySQL/MariaDB, and MS SQL Server
> 
> 
> Have fun,
> 
> Patrick


  reply	other threads:[~2024-10-28 13:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28 13:49 [gentoo-dev] RFC: New PostgreSQL categories Patrick Lauer
2024-10-28 13:57 ` Miroslav Šulc (fordfrog) [this message]
2024-10-28 13:59 ` Volkmar W. Pogatzki
2024-10-28 14:08 ` Agostino Sarubbo
2024-10-28 14:10 ` Azamat Hackimov
2024-10-28 15:21 ` Michał Górny
2024-10-28 17:07   ` Patrick Lauer
2024-10-28 19:15 ` Ulrich Müller
2024-10-29 22:22 ` Haelwenn (lanodan) Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1c00d0e4f449e078ecd7d6ae2e7111d6@gentoo.org \
    --to=fordfrog@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=patrick@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox