home.social

Search

68 results for “pgexperts”

  1. PGX @pgexperts ·

    PGConf.EU 2026 CFP closes Monday, June 1. Conference is October 20-23 in Valencia.

    If you have spent the last year solving a real Postgres problem (not a textbook one), submit it. The European Postgres audience reads commit messages and asks better questions when you skip the marketing deck.

    postgresql.org/about/news/call

    pgexperts.com

  2. PGX @pgexperts ·

    PGXpertise™ lets you have a world-leading PostgreSQL Expert on call. This is a monthly retainer service that provides a block of consulting hours that can be used for any service PGX provides, at a significant discount. Contact us today!

    pgexperts.com/services/pgxpert

    #postgresql #postgres
  3. PGX @[email protected] ·

    PGXpertise™ lets you have a world-leading PostgreSQL Expert on call. This is a monthly retainer service that provides a block of consulting hours that can be used for any service PGX provides, at a significant discount. Contact us today!

    pgexperts.com/services/pgxpert

    #PostgreSQL #postgres

    #postgresql #postgres
  4. PGX @[email protected] ·

    PGXpertise™ lets you have a world-leading PostgreSQL Expert on call. This is a monthly retainer service that provides a block of consulting hours that can be used for any service PGX provides, at a significant discount. Contact us today!

    pgexperts.com/services/pgxpert

    #PostgreSQL #postgres

    #postgresql #postgres
  5. PGX @pgexperts ·

    PgBouncer 1.25.2 shipped May 8 and patches CVE-2026-6664 — a pre-auth crash via a malformed SCRAM packet. Three other CVEs in the same release.

    If PgBouncer is reachable from anything you don't fully trust, upgrade this week.

    pgbouncer.org/2026/05/pgbounce

    PGX does PgBouncer hardening and connection-pool audits — pgexperts.com.

  6. PGX @pgexperts ·

    CVE-2026-2005 and CVE-2026-2006 are pgcrypto RCEs that have been latent since 2005. Fixes shipped in February; the full technical write-ups landed May 4.
    Unpatched fleets are now genuinely exposed. CVSS 8.8.

    postgresql.org/support/securit

    PGX reviews extension exposure and database security posture — pgexperts.com.

  7. PGX @pgexperts ·

    May 18: Supabase disables pg_graphql by default. May 30: the Data API flips to opt-out.

    Existing projects unchanged — every public-schema grant is still an API endpoint.

    supabase.com/changelog/45702-d

    PGX runs these audits: pgexperts.com

  8. PGX @pgexperts ·

    PGConf.dev 2026 is next week: May 19–22 at SFU Vancouver.

    Schedule was published recently. Even if you can't make it, watching what committers are talking about is the cleanest signal for what lands in PG19 and PG20.

    2026.pgconf.dev/

    Want a post-conference debrief filtered for "what actually affects production"?

    pgexperts.com

  9. PGX @pgexperts ·

    pgBackRest has been archived since April 27. The rescue-or-fork rumour mill has not yet produced a primary-source statement.
    The forward question for any production site: which backup tool's guarantees can a single maintainer realistically keep? Manifests, async, encryption, page-level incrementals — pick what you need, not what is familiar.

    lwn.net/Articles/1069951/

    If you are rebuilding your backup posture, that is PGX work.

    → pgexperts.com

    #postgresql #postgres #backupandrecovery
  10. PGX @pgexperts ·

    pg_lake makes Postgres talk to Apache Iceberg directly.

    The interesting question isn't "can it" — it's what happens on concurrent INSERTs: manifest commits, snapshot isolation, object-store consistency. Each one is a place the design has to make real trade-offs.

    github.com/Snowflake-Labs/pg_l

    Evaluating pg_lake for production? We can help: pgexperts.com.

  11. PGX @pgexperts ·

    pgvector 0.8.2 is out, fixing CVE-2026-3172 — a buffer overflow in the parallel HNSW build path. Backend crash or cross-relation data exposure in the worst case.

    If you bumped pgvector independently of your server version (very common in RAG stacks), yesterday's PG minor release doesn't carry you. Check the installed pgvector explicitly.

    postgresql.org/about/news/pgve

    Need a second set of eyes on a production pgvector deployment? pgexperts.com

  12. PGX @pgexperts ·

    PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 shipped May 14 — 11 security fixes plus 60+ bugs, headlined by CVE-2026-6473 (integer-wraparound RCE, CVSS 8.8).

    Also: covert timing-channel fix in MD5 password comparison. scram-sha-256 unaffected. Yet another reason to retire md5 auth.

    Release: postgresql.org/about/news/post

    If you want a second set of eyes on patch sequencing across primaries, replicas, and a logical-rep topology: pgexperts.com

  13. PGX @pgexperts ·

    PostgreSQL 19 went into feature freeze on April 8. Beta 1 is expected this month; GA targeted for September.

    Marquee items: SQL/PGQ, REPACK CONCURRENTLY, partition split/merge improvements.

    The beta window is when regressions show up cheaply. Use it.

    Devel notes: postgresql.org/docs/devel/rele

    If you want a structured PG19 evaluation against your workload before September: pgexperts.com

  14. PGX @pgexperts ·

    Flex Consulting™ provides organizations with highly experienced on-demand PostgreSQL resources without a monthly commitment. Each annual plan includes a block of consulting hours, which are available for any service PGX provides.

    pgexperts.com/services/consult

    #postgresql #postgres
  15. PGX @pgexperts ·

    Percona has shipped OSS Transparent Data Encryption patches for PostgreSQL. Until now, production TDE has mostly meant a proprietary or EDB dependency.

    Things to pin down before you adopt: where the cipher boundary sits (pages, WAL, TOAST, temp), key-rotation mechanics, throughput cost on bulk loads.

    Background: opensourceforu.com/2026/02/per

    If TDE is on your compliance checklist but vendor lock-in isn't on the menu: pgexperts.com

  16. PGX @pgexperts ·

    PGConf.dev 2026 is mid-flight at SFU Vancouver — talks today and tomorrow, unconference Friday, plus 30th-anniversary programming.

    If you're there, this is the room where next year's PostgreSQL is being argued out in real time.

    2026.pgconf.dev/

    PGX is in the community and around the room.

    pgexperts.com

  17. PGX @pgexperts ·

    Team PGX had a great week at PGConf DEV! We’re looking forward to following up on connections and implementing new knowledge and ideas. Stay tuned for the latest from PGX!

    pgexperts.com/

    #postgresql #postgres
  18. PGX @pgexperts ·

    PGConf.EU 2026 CFP closes Monday, June 1 at 23:59:59 UTC. Three-proposal limit per speaker, speaker notifications July 3, conference in Valencia October 20–22.

    2026.pgconf.eu/call-for-papers/

    If you want a read on a talk abstract before you submit — pgexperts.com.

  19. PGX @pgexperts ·

    pgvector 0.8.2 patches CVE-2026-3172 — a parallel-HNSW-build buffer overflow that can leak data across relations or crash the backend.

    Parallel HNSW is now the default in most production deployments. Patch this week.

    postgresql.org/about/news/pgve

    If you operate pgvector at scale and want a second opinion on your index strategy — pgexperts.com.

  20. PGX @pgexperts ·

    pgvector 0.8.2 patches CVE-2026-3172 — buffer overflow in parallel HNSW index builds, can leak data from other relations or crash the server.

    If you build HNSW indexes with parallelism enabled (most people do), upgrade this week.

    postgresql.org/about/news/pgve

    Want a second look at your vector-index strategy?

    pgexperts.com

  21. PGX @pgexperts ·

    PgBouncer 1.25.2 fixes four CVEs. Two of them (CVE-2026-6664 and CVE-2026-6665) are reachable pre-auth and crash the pooler from a single SCRAM packet.

    If your pooler is behind an unfiltered LB, patch this week.

    pgbouncer.org/2026/05/pgbounce

    PGX runs pgbouncer-fleet upgrades without taking production down.

    pgexperts.com

  22. Lutin Discret @[email protected] ·

    Je découvre cette collection de scripts qui permet de maintenir les indexes d'une base #postgresql (index manquants, dupliqués, inutiles...)

    Merci @l_avrot 👍

    github.com/pgexperts/pgx_scrip

    #pgsession16

    #postgresql #pgsession16
  23. PgDay Boston @PgDayBoston ·

    Thank you PGX for your Silver sponsorship! Your generous support makes community events like PgDay Boston possible!

    pgexperts.com/

    #postgresql #postgres #sponsor
  24. Lutin Discret @[email protected] ·

    Je découvre cette collection de scripts qui permet de maintenir les indexes d'une base #postgresql (index manquants, dupliqués, inutiles...)

    Merci @l_avrot 👍

    github.com/pgexperts/pgx_scrip

    #pgsession16

    #postgresql #pgsession16
  25. Lutin Discret @[email protected] ·

    Je découvre cette collection de scripts qui permet de maintenir les indexes d'une base #postgresql (index manquants, dupliqués, inutiles...)

    Merci @l_avrot 👍

    github.com/pgexperts/pgx_scrip

    #pgsession16

    #postgresql #pgsession16
  26. Lutin Discret @[email protected] ·

    Je découvre cette collection de scripts qui permet de maintenir les indexes d'une base #postgresql (index manquants, dupliqués, inutiles...)

    Merci @l_avrot 👍

    github.com/pgexperts/pgx_scrip

    #pgsession16

    #pgsession16 #postgresql
  27. Lutin Discret @[email protected] ·

    Je découvre cette collection de scripts qui permet de maintenir les indexes d'une base #postgresql (index manquants, dupliqués, inutiles...)

    Merci @l_avrot 👍

    github.com/pgexperts/pgx_scrip

    #pgsession16

    #postgresql #pgsession16
  28. PGX @pgexperts ·

    Our CEO, Christophe Pettus, will be giving his talk “Why is Postgres Terrible” on Tuesday, May 19th at PGConf.dev! That’s 5 days away! The countdown is on!

    2026.pgconf.dev/session/658

    #postgresql #postgres #conference
  29. PGX @pgexperts ·

    PGX is proud to be a Silver Sponsor for PgDay Boston!

    2026.pgdayboston.org/sponsors/

    #postgresql #postgres #sponsorship
  30. PGX @pgexperts ·

    PGX is proud to be a Silver Sponsor for PgDay Boston!

    2026.pgdayboston.org/sponsors/

    #postgresql #postgres #sponsorship
Next page