Collation Conundrum | Scaling Postgres 307
Join Over 1,000 Engineers & Get New Episodes Weekly!
In this episode of Scaling Postgres, we discuss whether we should be using bytewise or linguistic ordering by default, how to transform data in Postgres, benefits of a transaction_timeout and how to enforce join order.
Content Discussed
- Using binary-sorted indexes
- Transforming and Analyzing Data in PostgreSQL
- transaction_timeout
- Enforcing join orders in PostgreSQL
- Speed up PostgreSQL® pgvector queries with indexes
- How to use pgbench to test PostgreSQL® performance
- Trying Out CloudNative-PG: A Novice in a Kubernetes World
- CloudNativePG Recipe 2 - Inspecting Default Resources in a CloudNativePG Cluster
- CloudNativePG Recipe 3 - What!?! No superuser access?
- Managing Time Series Data Using TimeScaleDB-Powered PostgreSQL
- Artur Zakirov
- Rails + Postgres Postgres.FM 086 — Extended blog post edition!
- Tuning random_page_cost and how index correlation affects query plans
- The importance of PostgreSQL timelines
- Connecting QGIS to Postgres and PostGIS
- Data Navigation with PostgreSQL Cursors – Part III
- Less is More
- IN, OUT and INOUT parameters in Oracle vs PostgreSQL
- Setting up a debugging environment in PostgreSQL to better understand OpenSSL APIs
- Recovery Hack: Restoring Tablespace Using Barman on Windows
- Using Polars & DuckDB with Postgres
- February 20 recording – finally!
- PostgreSQL March Meetup in Berlin
- Postgres Columnstore index vs. ClickHouse for analytics
- Migrating a Low-Code IoT Platform Storing 20M Records/Day
- How We Are Building a Self-Sustaining Open-Source Business in the Cloud Era
- Announcing Tembo CLI: Infrastructure as code for the Postgres ecosystem
- Better Postgres with Prisma Experience
- Unveiling the New Timescale Community Templates
YouTube Video
Podcast Audio
