# PlanetScale

Posts about the PlanetScale platform, MySQL, PostgreSQL, databases, and more.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## PlanetScale ranks #24 in Deloitte's Technology Fast 500

DevFeed: [PlanetScale ranks #24 in Deloitte's Technology Fast 500](<https://devfeed.tech/articles/planetscale-ranks-24-in-deloitte-s-technology-fast-500-142354.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/planetscale-ranks-24-in-deloittes-technology-fast-500>)

Author: Holly Guevara

Published: 2026-11-18T00:00:00Z

Content type: news

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [neki](<https://devfeed.tech/topics/neki.md>), [database-optimization](<https://devfeed.tech/topics/database-optimization.md>)

Tags: [2022](<https://devfeed.tech/tags/2022.md>), [2023](<https://devfeed.tech/tags/2023.md>), [2025](<https://devfeed.tech/tags/2025.md>), [2026](<https://devfeed.tech/tags/2026.md>), [aws](<https://devfeed.tech/tags/aws.md>), [azure](<https://devfeed.tech/tags/azure.md>), [cash-app](<https://devfeed.tech/tags/cash-app.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-services](<https://devfeed.tech/tags/cloud-services.md>), [company](<https://devfeed.tech/tags/company.md>), [database](<https://devfeed.tech/tags/database.md>), [databases](<https://devfeed.tech/tags/databases.md>), [deloitte](<https://devfeed.tech/tags/deloitte.md>), [developers](<https://devfeed.tech/tags/developers.md>), [downtime](<https://devfeed.tech/tags/downtime.md>), [fast](<https://devfeed.tech/tags/fast.md>), [growth](<https://devfeed.tech/tags/growth.md>), [north-america](<https://devfeed.tech/tags/north-america.md>), [planetscale](<https://devfeed.tech/tags/planetscale.md>), [ranking](<https://devfeed.tech/tags/ranking.md>), [technology](<https://devfeed.tech/tags/technology.md>)

### AI overview

PlanetScale ranked #24 on Deloitte's 2026 Technology Fast 500 after revenue grew 3,493% from fiscal 2022 to fiscal 2025; the company says it ranked first in cloud services and previously placed #188 in 2023. Since then, it expanded from a MySQL platform to include Postgres and Neki, its sharded Postgres offering. The text highlights Metal's locally attached NVMe storage, Postgres availability and entry pricing from $5/month, Neki's sharding and online operations features, Postgres query resource budgets through Traffic Control, and Azure availability alongside AWS and GCP.

### Source excerpt

PlanetScale is #24 on the 2026 Deloitte Technology Fast 500, a ranking of the fastest-growing technology companies in North America.

## Introducing Insights Agent

DevFeed: [Introducing Insights Agent](<https://devfeed.tech/articles/introducing-insights-agent-139723.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/introducing-insights-agent>)

Author: Enrique Gonzalez

Published: 2026-11-17T00:00:00Z

Content type: release

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Agent Harness](<https://devfeed.tech/topics/agent-harness.md>), [agent observability](<https://devfeed.tech/topics/agent-observability.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [cli](<https://devfeed.tech/tags/cli.md>), [cloud-agents](<https://devfeed.tech/tags/cloud-agents.md>), [code](<https://devfeed.tech/tags/code.md>), [connect](<https://devfeed.tech/tags/connect.md>), [cursor-origin](<https://devfeed.tech/tags/cursor-origin.md>), [insights](<https://devfeed.tech/tags/insights.md>), [product](<https://devfeed.tech/tags/product.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [queries](<https://devfeed.tech/tags/queries.md>), [recommendations](<https://devfeed.tech/tags/recommendations.md>), [schema](<https://devfeed.tech/tags/schema.md>)

### AI overview

PlanetScale Insights Agent investigates database performance issues using a database's schema, Query Insights data, and connected repository, then opens a pull request when evidence supports a change. Its two focused run types address slow queries and recommendations; runs can be started on demand or scheduled, and may propose changes across multiple files. It follows repository conventions, and Vitess runs can also open a deploy request. Changes are suggestions: nothing is automatically merged or deployed. Runs are billed when completed, with organization spend limits available; the temporary sandbox exists only during a run. PlanetScale's built-in agent offers curated prompts and managed setup, while the CLI and MCP server let teams build their own automations with custom prompts and more control. At launch, one GitHub or Cursor Origin repository can connect to each database. The feature is on by default but acts only after a repository is connected.

### Source excerpt

Insights Agent connect to your codebase to turn slow queries and schema recommendations into pull requests.

## How we migrate TBs from Heroku without logical replication

DevFeed: [How we migrate TBs from Heroku without logical replication](<https://devfeed.tech/articles/how-we-migrate-tbs-from-heroku-without-logical-replication-130264.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/migrate-from-heroku-to-planetscale>)

Author: Dmitrii Anisovich

Published: 2026-11-11T00:00:00Z

Content type: tutorial

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [Heroku Postgres](<https://devfeed.tech/topics/heroku-postgres.md>), [Heroku](<https://devfeed.tech/topics/heroku.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [copy](<https://devfeed.tech/topics/copy.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [downtime](<https://devfeed.tech/tags/downtime.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [heroku](<https://devfeed.tech/tags/heroku.md>), [logical](<https://devfeed.tech/tags/logical.md>), [logical-replication](<https://devfeed.tech/tags/logical-replication.md>), [migrate](<https://devfeed.tech/tags/migrate.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [replication](<https://devfeed.tech/tags/replication.md>)

### AI overview

Heroku's standard Postgres plans lack logical replication, so PlanetScale's open-source Heroku Migrator uses Bucardo triggers to capture writes while it copies data and keeps the target in sync. The process starts with read-only discovery via ps-discovery and a Liftoff assessment; replicated tables need a primary key or unique index, and schema changes must be frozen during migration. After copying, the migrator rebuilds secondary and unique indexes in parallel, verifies schema and data checks, then supports a controlled traffic switch and rollback. For large migrations, version 2.0 addresses repeated full-copy restarts by separating data transfer from index rebuilding, uses TCP keepalives to detect dropped long-lived connections, and adds txntime indexes to Bucardo track tables to speed replication checks. The article reports a sample copy rate increase from about 60 to nearly 300 GB/hour, with index rebuilding taking about two hours; results depend on the database and migration conditions.

### Source excerpt

We've equipped our customers with an open source tool that not only quickly transfers your data but also provides a replication-based experience, so that any user can migrate from Heroku without extended downtime or the need to purchase a third-party product.

## Designing a reliable unplanned failover

DevFeed: [Designing a reliable unplanned failover](<https://devfeed.tech/articles/designing-a-reliable-unplanned-failover-121334.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/designing-a-reliable-unplanned-failover>)

Author: Shlomi Noach

Published: 2026-11-05T00:00:00Z

Content type: article

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [read-replica](<https://devfeed.tech/topics/read-replica.md>), [Availability](<https://devfeed.tech/topics/availability.md>), [distributed algorithm](<https://devfeed.tech/topics/distributed-algorithm.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>)

Tags: [admin](<https://devfeed.tech/tags/admin.md>), [detection](<https://devfeed.tech/tags/detection.md>), [durability](<https://devfeed.tech/tags/durability.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [failover](<https://devfeed.tech/tags/failover.md>), [freeze](<https://devfeed.tech/tags/freeze.md>), [neki](<https://devfeed.tech/tags/neki.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [primary](<https://devfeed.tech/tags/primary.md>), [wal](<https://devfeed.tech/tags/wal.md>)

### AI overview

Neki avoids promoting a replica based on Admin's failed health check alone. It compares replica reports of physical replication: a reachable replica still streaming from the primary blocks failover, while a reachable report of broken replication with no contradiction supports recovery; if Admin cannot reach any replica, it waits. Once it decides the primary is dead, Neki disconnects reachable replicas by changing `primary_conninfo`, preventing reconnection to a returning primary and freezing their WAL positions. Admin prefers a promotable replica that has replayed through the highest received WAL position, waits briefly for catch-up, then selects by `receive_lsn` and `replay_lsn`. The new primary is promoted and the others repointed; a replica ahead of it may need rewind or rebuild. With synchronous `ANY 1`, commits require an acknowledging replica, but acknowledged WAL can still be lost if the primary and the replica holding it fail together. Cross-availability-zone acknowledgements reduce that risk at the cost of commit latency. Async durability offers no guarantee that an unreachable primary has stopped accepting writes. Unrecoverable cases include having no reachable candidate.

### Source excerpt

How Neki detects a failed Postgres primary, and chooses a new one from the WAL that survived.

## The hidden latency inside your database

DevFeed: [The hidden latency inside your database](<https://devfeed.tech/articles/the-hidden-latency-inside-your-database-117164.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/the-hidden-latency-inside-your-database>)

Author: Simeon Griggs

Published: 2026-11-03T00:00:00Z

Content type: article

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [database-optimization](<https://devfeed.tech/topics/database-optimization.md>), [Amazon Elastic Block Store (Amazon EBS)](<https://devfeed.tech/topics/amazon-elastic-block-store-amazon-ebs.md>), [Database](<https://devfeed.tech/topics/database.md>), [RAID](<https://devfeed.tech/topics/raid.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-storage](<https://devfeed.tech/tags/cloud-storage.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [compute](<https://devfeed.tech/tags/compute.md>), [database](<https://devfeed.tech/tags/database.md>), [durability](<https://devfeed.tech/tags/durability.md>), [ebs](<https://devfeed.tech/tags/ebs.md>), [ec2](<https://devfeed.tech/tags/ec2.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [latency](<https://devfeed.tech/tags/latency.md>), [network-attached-storage](<https://devfeed.tech/tags/network-attached-storage.md>), [storage](<https://devfeed.tech/tags/storage.md>)

### AI overview

The article explains that EBS-backed databases incur network latency on each disk operation, while local NVMe storage avoids that hop for reads. PlanetScale Metal addresses local disks' usual durability and flexibility limits with a primary and at least two replicas across availability zones; a write is acknowledged only after at least one replica confirms it, and a replica can be promoted on failure. The article says this adds one network hop per commit, while reads remain local. It contrasts this with EBS IOPS limits and gives an example where a local-NVMe instance is described as both cheaper and capable of higher IOPS than an EBS configuration. Metal may help when frequent cache misses or IOPS limits bottleneck a workload; if reads mostly fit in RAM and writes are low, the article says network-attached storage may be sufficient. These are the article's claims and examples, not a universal performance guarantee.

### Source excerpt

Network-attached storage is a fine choice and a bad default.

## Designing a planned switchover for minimum disruption

DevFeed: [Designing a planned switchover for minimum disruption](<https://devfeed.tech/articles/designing-a-planned-switchover-for-minimum-disruption-106760.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/designing-a-planned-switchover-for-minimum-disruption>)

Author: Shlomi Noach

Published: 2026-10-29T00:00:00Z

Content type: article

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [neki](<https://devfeed.tech/topics/neki.md>), [downtime](<https://devfeed.tech/topics/downtime.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [Resilience](<https://devfeed.tech/topics/resilience.md>), [distributed algorithm](<https://devfeed.tech/topics/distributed-algorithm.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [health check](<https://devfeed.tech/topics/health-check.md>)

Tags: [admin](<https://devfeed.tech/tags/admin.md>), [buffer](<https://devfeed.tech/tags/buffer.md>), [candidate](<https://devfeed.tech/tags/candidate.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [client](<https://devfeed.tech/tags/client.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [commit](<https://devfeed.tech/tags/commit.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [convergence](<https://devfeed.tech/tags/convergence.md>), [disruption](<https://devfeed.tech/tags/disruption.md>), [durability](<https://devfeed.tech/tags/durability.md>), [election](<https://devfeed.tech/tags/election.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [failover](<https://devfeed.tech/tags/failover.md>), [ha](<https://devfeed.tech/tags/ha.md>), [neki](<https://devfeed.tech/tags/neki.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [primary](<https://devfeed.tech/tags/primary.md>), [query](<https://devfeed.tech/tags/query.md>), [replication](<https://devfeed.tech/tags/replication.md>), [rollback](<https://devfeed.tech/tags/rollback.md>)

### AI overview

Neki reduces disruption during planned Postgres primary switchovers by validating the shard and candidate while the old primary still serves writes, then buffering primary-bound queries before making it read-only. Admin selects a replica, disconnects the others to establish a final WAL position, and waits for the target to replay through it. With synchronous replication configured as `ANY 1`, the target can catch up without a slow replica blocking progress; Admin also prepares replication slots and requires at least one attached replica in the target's synchronous configuration. Routers replan buffered queries against the new topology, so they take longer but usually avoid errors. Failed checks or a deadline trigger rollback: the old primary can be made writable again and other replicas reconnected. Buffers have finite capacity and query deadlines, and not all Routers must acknowledge the buffering signal. Neki contrasts this with Patroni's clean-shutdown approach, which simplifies final WAL accounting but can leave no primary while the old server restarts or rewinds. Under Neki's synchronous durability policy and default `synchronous_commit = on`, acknowledged commits are present.

### Source excerpt

How Neki uses preflight checks, query buffering, synchronous replication, and fast rollback to make Postgres primary switchovers less disruptive.

## Shard design doesn't start from your tables

DevFeed: [Shard design doesn't start from your tables](<https://devfeed.tech/articles/shard-design-doesn-t-start-from-your-tables-98539.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/shard-groups-the-unit-of-co-location>)

Author: Rohit Nayak

Published: 2026-10-23T00:00:00Z

Content type: article

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [table-partitioning](<https://devfeed.tech/topics/table-partitioning.md>), [schema design](<https://devfeed.tech/topics/schema-design.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>), [rdbms](<https://devfeed.tech/topics/rdbms.md>), [JOIN](<https://devfeed.tech/topics/join.md>)

Tags: [64-bit](<https://devfeed.tech/tags/64-bit.md>), [aggregate](<https://devfeed.tech/tags/aggregate.md>), [algorithm](<https://devfeed.tech/tags/algorithm.md>), [atomic](<https://devfeed.tech/tags/atomic.md>), [best](<https://devfeed.tech/tags/best.md>), [can](<https://devfeed.tech/tags/can.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [change](<https://devfeed.tech/tags/change.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [column](<https://devfeed.tech/tags/column.md>), [commit](<https://devfeed.tech/tags/commit.md>), [concepts](<https://devfeed.tech/tags/concepts.md>), [copy](<https://devfeed.tech/tags/copy.md>), [cross](<https://devfeed.tech/tags/cross.md>), [customer](<https://devfeed.tech/tags/customer.md>), [design](<https://devfeed.tech/tags/design.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [key](<https://devfeed.tech/tags/key.md>), [neki](<https://devfeed.tech/tags/neki.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [queries](<https://devfeed.tech/tags/queries.md>), [tables](<https://devfeed.tech/tags/tables.md>), [transactions](<https://devfeed.tech/tags/transactions.md>)

### AI overview

Design shard groups around keys shared by important queries and transactions: co-locate related tables so joins and transactions stay on one shard. In Neki, matching shard keys and hashing place rows with the same key together; reference tables are copied to each listed shard, keeping joins local. Cross-shard transactions lack atomic commit and a shared snapshot. The article describes `xxhash` as its recommended index, `range` for direct integer ranges, and `modulo` as predictable but costly to change at scale. A global secondary index can support lookups by a non-shard key through two single-shard reads. MoveTables imports data and can create initial reference-table copies; Reshard changes shard keys or shard counts as query needs evolve.

### Source excerpt

Shard group design starts from your queries, not your tables. Find the key that your most important queries and transactions share, and put every table that carries that key in one group.

## I don't trust ON DELETE CASCADE

DevFeed: [I don't trust ON DELETE CASCADE](<https://devfeed.tech/articles/i-don-t-trust-on-delete-cascade-92987.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/i-dont-like-delete-cascade>)

Author: Tom Pang

Published: 2026-10-21T00:00:00Z

Content type: opinion

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [locking](<https://devfeed.tech/topics/locking.md>), [Database Migration](<https://devfeed.tech/topics/database-migration.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>), [rdbms](<https://devfeed.tech/topics/rdbms.md>), [schema design](<https://devfeed.tech/topics/schema-design.md>), [database-consistency](<https://devfeed.tech/topics/database-consistency.md>), [CRUD](<https://devfeed.tech/topics/crud.md>), [expand and contract migration](<https://devfeed.tech/topics/expand-and-contract-migration.md>)

Tags: [alter](<https://devfeed.tech/tags/alter.md>), [application](<https://devfeed.tech/tags/application.md>), [apply](<https://devfeed.tech/tags/apply.md>), [batch](<https://devfeed.tech/tags/batch.md>), [built-in](<https://devfeed.tech/tags/built-in.md>), [cascade](<https://devfeed.tech/tags/cascade.md>), [children](<https://devfeed.tech/tags/children.md>), [database](<https://devfeed.tech/tags/database.md>), [database-design](<https://devfeed.tech/tags/database-design.md>), [database-schema](<https://devfeed.tech/tags/database-schema.md>), [delete](<https://devfeed.tech/tags/delete.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [failure](<https://devfeed.tech/tags/failure.md>), [fast](<https://devfeed.tech/tags/fast.md>), [foreign-keys](<https://devfeed.tech/tags/foreign-keys.md>), [identity](<https://devfeed.tech/tags/identity.md>), [index](<https://devfeed.tech/tags/index.md>), [locking](<https://devfeed.tech/tags/locking.md>), [outage](<https://devfeed.tech/tags/outage.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [risk](<https://devfeed.tech/tags/risk.md>), [schema](<https://devfeed.tech/tags/schema.md>)

### AI overview

Large cascading deletes can stall PostgreSQL writes: they hold RowExclusiveLock on involved tables while generating row, index, and WAL changes; a migration requesting AccessExclusiveLock can then block later queries. The excerpt recommends short migration lock_timeouts with retries, indexing foreign keys, and, for large customer deletions, soft-deleting first and reaping rows later in small batches. It also describes logical-replication pitfalls: subscriber-side cascades are skipped by default, so subscriber-only child rows may be orphaned; published delete cascades can fail if a child table lacks replica identity. Replication setups should account for the full foreign-key tree, with separate cleanup for subscriber-only children. The excerpt notes soft deletes require application reads to honor deleted_at, but allow controlled cleanup and possible restoration.

### Source excerpt

A one-line convenience in your database schema can become an outage. There are better ways to delete data that won't risk locking up your database.

## Neki update: $50 Metal, read-only replicas, Azure, and more

DevFeed: [Neki update: $50 Metal, read-only replicas, Azure, and more](<https://devfeed.tech/articles/neki-update-50-metal-read-only-replicas-azure-and-more-91077.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/neki-updates-and-preparing-for-production>)

Author: Nick Van Wiggeren

Published: 2026-10-20T04:00:00Z

Content type: release

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [neki](<https://devfeed.tech/topics/neki.md>), [read-replica](<https://devfeed.tech/topics/read-replica.md>), [Azure](<https://devfeed.tech/topics/azure.md>)

Tags: [azure](<https://devfeed.tech/tags/azure.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [metal](<https://devfeed.tech/tags/metal.md>), [neki](<https://devfeed.tech/tags/neki.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [preview](<https://devfeed.tech/tags/preview.md>), [product](<https://devfeed.tech/tags/product.md>), [update](<https://devfeed.tech/tags/update.md>)

### AI overview

Since Neki's platform preview opened, PlanetScale added read-only shard replicas and Metal instances starting at $50/month, including a 1/8-vCPU, 1-GB RAM, 10-GB NVMe option. The excerpt highlights broad query-layer improvements for running existing SQL on sharded Postgres, standard-tool exports via COPY, and faster bulk writes: distributed INSERT ... SELECT is about 76x faster than at launch, and COPY ingest roughly 5x faster. EXPLAIN (NEKI_PG_PLAN) shows both Neki's distributed plan and each shard's Postgres plan in a format supported by common Postgres explain tools. Other additions include Terraform and CLI extension management, branch metrics through MCP, Azure regions for Neki and Postgres, router parameter management, CLI indicators for updates, and huge pages on supported sizes, which require a restart. Neki remains in platform preview; the excerpt recommends contacting PlanetScale to evaluate it for workloads.

### Source excerpt

Postgres compatibility, read-only replicas, smaller Metal instances, Azure, and more have landed for Neki since platform preview.

## Sequences and other volatiles in Neki

DevFeed: [Sequences and other volatiles in Neki](<https://devfeed.tech/articles/sequences-and-other-volatiles-in-neki-87047.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/neki-volatile-expressions>)

Author: Mats Rydberg

Published: 2026-10-14T00:00:00Z

Content type: article

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [neki](<https://devfeed.tech/topics/neki.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>), [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>)

Tags: [cardinality](<https://devfeed.tech/tags/cardinality.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [neki](<https://devfeed.tech/tags/neki.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>)

### AI overview

The article explains how Neki, PlanetScale's sharded Postgres system, handles PostgreSQL sequences and other volatile expressions across shards. It describes why sequence operations require centralized router evaluation, how expression volatility and row cardinality affect evaluation, and how Neki processes updates that need sequence values.

### Source excerpt

How Neki evaluates PostgreSQL volatile expressions with the right cardinality to preserve sequence semantics across shards.

## PlanetScale is now available on Azure

DevFeed: [PlanetScale is now available on Azure](<https://devfeed.tech/articles/planetscale-is-now-available-on-azure-86167.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/planetscale-is-now-on-azure>)

Author: Matt Layher

Published: 2026-10-13T00:00:00Z

Content type: release

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [Azure](<https://devfeed.tech/topics/azure.md>), [DuckDB](<https://devfeed.tech/topics/duckdb.md>), [Azure Kubernetes Service](<https://devfeed.tech/topics/azure-kubernetes-service.md>), [Azure Arc](<https://devfeed.tech/topics/azure-arc.md>), [Python Driver for SQL Server](<https://devfeed.tech/topics/python-driver-for-sql-server.md>)

Tags: [azure](<https://devfeed.tech/tags/azure.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-regions](<https://devfeed.tech/tags/cloud-regions.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [cni](<https://devfeed.tech/tags/cni.md>), [company](<https://devfeed.tech/tags/company.md>), [database](<https://devfeed.tech/tags/database.md>), [high-availability](<https://devfeed.tech/tags/high-availability.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [ip](<https://devfeed.tech/tags/ip.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [latency](<https://devfeed.tech/tags/latency.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [product](<https://devfeed.tech/tags/product.md>)

### AI overview

PlanetScale launched support for PlanetScale Postgres and Neki databases on Microsoft Azure in select regions. The release describes Azure Kubernetes networking changes that assign pod IPs in blocks, increasing stated network capacity 16-fold, and notes that Vitess databases are not yet available on Azure.

### Source excerpt

PlanetScale Postgres and Neki databases can now be deployed on Microsoft Azure

## What gets TOASTed in Postgres

DevFeed: [What gets TOASTed in Postgres](<https://devfeed.tech/articles/what-gets-toasted-in-postgres-85435.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/what-gets-toasted-in-postgres>)

Author: Ahmed Darwich

Published: 2026-10-12T00:00:00Z

Content type: article

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [Compression](<https://devfeed.tech/topics/compression.md>), [xz](<https://devfeed.tech/topics/xz.md>)

Tags: [engineering](<https://devfeed.tech/tags/engineering.md>), [it](<https://devfeed.tech/tags/it.md>), [lz4](<https://devfeed.tech/tags/lz4.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [postgres-19](<https://devfeed.tech/tags/postgres-19.md>), [toast](<https://devfeed.tech/tags/toast.md>)

### AI overview

The article explains when PostgreSQL TOAST compresses or moves variable-length values, and compares pglz with LZ4. LZ4 is faster and can reduce storage, but may compress less effectively and slow some reads. PostgreSQL 19 switches the default TOAST compression to LZ4 in builds with LZ4 support.

### Source excerpt

Postgres 19 switches TOAST compression from pglz to LZ4. LZ4 is faster, but it isn't always smaller, and some reads get slower with it.

## TIN v1.0.6: 2-3x faster, with support for stemming

DevFeed: [TIN v1.0.6: 2-3x faster, with support for stemming](<https://devfeed.tech/articles/tin-v1-0-6-2-3x-faster-with-support-for-stemming-77311.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/tin-v106>)

Author: Eric Ridge

Published: 2026-10-08T00:00:00Z

Content type: release

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [Cache](<https://devfeed.tech/topics/cache.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>)

Tags: [1-4](<https://devfeed.tech/tags/1-4.md>), [arm64](<https://devfeed.tech/tags/arm64.md>), [avx](<https://devfeed.tech/tags/avx.md>), [concurrent](<https://devfeed.tech/tags/concurrent.md>), [ec2](<https://devfeed.tech/tags/ec2.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [postgres](<https://devfeed.tech/tags/postgres.md>)

### AI overview

TIN v1.0.6 adds stemming support for 18 languages and uses the block-max plan for searches with deterministic tiebreakers. PlanetScale reports benchmark results showing TIN outperforming ParadeDB across the tested query types on x86-64 and ARM64. The release is rolling out to customers, and existing indexes do not need to be rebuilt for the v1.0.6 performance improvements.

### Source excerpt

TIN v1.0.6 supports stemming in 18 languages and is 2-3x as fast as the GA version

## Admission control in software: leaky buckets and Postgres traffic management

DevFeed: [Admission control in software: leaky buckets and Postgres traffic management](<https://devfeed.tech/articles/what-today-s-software-owes-to-bronze-age-clocks-66825.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/leaky-buckets-in-software-explained>)

Author: Simeon Griggs

Published: 2026-10-07T00:00:00Z

Content type: article

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [alert triage](<https://devfeed.tech/topics/alert-triage.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>), [observability](<https://devfeed.tech/topics/observability.md>)

Tags: [admission](<https://devfeed.tech/tags/admission.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [database](<https://devfeed.tech/tags/database.md>), [databases](<https://devfeed.tech/tags/databases.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [software](<https://devfeed.tech/tags/software.md>)

### AI overview

Leaky buckets are a low-overhead way to regulate work in software by tracking capacity and replenishing it over time. The article explains their use in rate limiting and describes PlanetScale's Database Traffic Control for Postgres, which estimates query costs and uses configurable resource budgets to warn about or block queries before they run.

### Source excerpt

Admission controls in software determine what does or doesn't happen next, and the most common implementation has ancient roots.

## Introducing Dedicated Read Replicas for Postgres

DevFeed: [Introducing Dedicated Read Replicas for Postgres](<https://devfeed.tech/articles/introducing-dedicated-read-replicas-for-postgres-65647.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/introducing-postgres-dedicated-read-replicas>)

Author: Chris Sinjakli

Published: 2026-10-06T00:00:00Z

Content type: release

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [read-replica](<https://devfeed.tech/topics/read-replica.md>), [consistency](<https://devfeed.tech/topics/consistency.md>)

Tags: [data-centers](<https://devfeed.tech/tags/data-centers.md>), [end-user-experience](<https://devfeed.tech/tags/end-user-experience.md>), [performance](<https://devfeed.tech/tags/performance.md>), [pgvector](<https://devfeed.tech/tags/pgvector.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [product](<https://devfeed.tech/tags/product.md>), [queries](<https://devfeed.tech/tags/queries.md>), [read-replicas](<https://devfeed.tech/tags/read-replicas.md>), [traffic](<https://devfeed.tech/tags/traffic.md>)

### AI overview

PlanetScale introduces dedicated asynchronous Postgres read replicas that customers can create, size, and connect to independently. They can route regional traffic to replicas to reduce read latency or isolate workloads such as vector search and analytics from primary database traffic. Replicas are configurable through the dashboard, API, or CLI.

### Source excerpt

Use dedicated read replicas to isolate read-only workloads and distribute your data across data centers around the world.

## Designing Neki for performance

DevFeed: [Designing Neki for performance](<https://devfeed.tech/articles/designing-neki-for-performance-63394.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/designing-neki-for-performance>)

Author: Dirkjan Bussink

Published: 2026-10-01T00:00:00Z

Content type: article

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [scalable-architecture](<https://devfeed.tech/topics/scalable-architecture.md>), [database-optimization](<https://devfeed.tech/topics/database-optimization.md>)

Tags: [engineering](<https://devfeed.tech/tags/engineering.md>), [neki](<https://devfeed.tech/tags/neki.md>), [performance](<https://devfeed.tech/tags/performance.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>)

### AI overview

Neki routes PostgreSQL queries across shards and improves performance by keeping result data in wire-format bytes until the router needs to inspect it. The article explains how lazy decoding, selective column handling, and byte-backed row representations reduce unnecessary work while supporting operations such as limits, sorting, projection, joins, and aggregation.

### Source excerpt

How Neki only decodes the parts of a PostgreSQL result the router actually needs.

## Sharding strategies for hot tenants and changing product needs

DevFeed: [Sharding strategies for hot tenants and changing product needs](<https://devfeed.tech/articles/handling-hot-shards-61223.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/hot-shards-hotter-tenants>)

Author: Simeon Griggs

Published: 2026-09-28T00:00:00Z

Content type: article

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [sharding](<https://devfeed.tech/topics/sharding.md>), [Per-user Database](<https://devfeed.tech/topics/per-user-database.md>)

Tags: [customer](<https://devfeed.tech/tags/customer.md>), [data](<https://devfeed.tech/tags/data.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [messaging](<https://devfeed.tech/tags/messaging.md>), [neki](<https://devfeed.tech/tags/neki.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [sharding](<https://devfeed.tech/tags/sharding.md>), [vitess](<https://devfeed.tech/tags/vitess.md>)

### AI overview

A sharding strategy that distributes tenants evenly can become ineffective when some tenants grow much larger or product needs introduce cross-tenant queries. The article describes how these pressures can overload shards and complicate scaling, using Slack's changing workspace sharding needs as an example.

### Source excerpt

What makes a good sharding strategy today might not work so well tomorrow. What happens when you have one tenant hitting your database orders of magnitude more than any other? Or product managers knocking down your door with new requirements? If you're already on Neki, fortunately these are issues we can solve.

## When to choose x86-64 vs aarch64

DevFeed: [When to choose x86-64 vs aarch64](<https://devfeed.tech/articles/when-to-choose-x86-64-vs-aarch64-60022.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/when-to-choose-x86-64-vs-aarch64>)

Author: Ahmed Darwich

Published: 2026-09-25T00:00:00Z

Content type: article

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [Arm](<https://devfeed.tech/topics/arm.md>), [x86-64](<https://devfeed.tech/topics/x86-64.md>), [cpu](<https://devfeed.tech/topics/cpu.md>), [Database](<https://devfeed.tech/topics/database.md>), [PlanetScale](<https://devfeed.tech/topics/planetscale.md>), [x86](<https://devfeed.tech/topics/x86.md>), [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [architectures](<https://devfeed.tech/tags/architectures.md>), [arm](<https://devfeed.tech/tags/arm.md>), [aws](<https://devfeed.tech/tags/aws.md>), [chip](<https://devfeed.tech/tags/chip.md>), [chips](<https://devfeed.tech/tags/chips.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [google](<https://devfeed.tech/tags/google.md>), [graviton](<https://devfeed.tech/tags/graviton.md>), [low-power](<https://devfeed.tech/tags/low-power.md>), [neki](<https://devfeed.tech/tags/neki.md>), [performance](<https://devfeed.tech/tags/performance.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [power](<https://devfeed.tech/tags/power.md>), [processor](<https://devfeed.tech/tags/processor.md>), [x86](<https://devfeed.tech/tags/x86.md>), [x86-64](<https://devfeed.tech/tags/x86-64.md>)

### AI overview

This article explains how x86-64 and Arm server architectures differ for PlanetScale Postgres and Neki databases. It covers vCPU definitions, hyperthreading, power efficiency, and how workload concurrency affects performance when choosing a cloud database architecture.

### Source excerpt

ARM and x86 can give you different performance at the same vCPU count. Here's what differs, what to measure, and how to choose.

## Upgrading a Hacker News Search App to TIN for Faster Postgres Full-Text Search

DevFeed: [Upgrading a Hacker News Search App to TIN for Faster Postgres Full-Text Search](<https://devfeed.tech/articles/tin-postgres-search-is-faster-better-and-cheaper-58761.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/searching-hn-with-tin>)

Author: Patrick Reynolds

Published: 2026-09-23T00:00:00Z

Content type: article

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [App](<https://devfeed.tech/topics/app.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>), [autocomplete](<https://devfeed.tech/topics/autocomplete.md>)

Tags: [autocomplete](<https://devfeed.tech/tags/autocomplete.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [faster](<https://devfeed.tech/tags/faster.md>), [full-text-search](<https://devfeed.tech/tags/full-text-search.md>), [optimized](<https://devfeed.tech/tags/optimized.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [queries](<https://devfeed.tech/tags/queries.md>), [search](<https://devfeed.tech/tags/search.md>)

### AI overview

The article demonstrates upgrading a Hacker News search app to TIN, a Postgres full-text search implementation. It discusses immediate query execution, wildcard searches, autocomplete, fuzzy matching, stop-word handling, and query performance.

### Source excerpt

A good Postgres search demo was doing the rounds online. Let's see what happens when we upgrade it to TIN.

## Anatomy of a (Postgres) search engine

DevFeed: [Anatomy of a (Postgres) search engine](<https://devfeed.tech/articles/anatomy-of-a-postgres-search-engine-58072.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/anatomy-of-a-postgres-search-engine>)

Author: Eric Ridge

Published: 2026-09-22T00:00:00Z

Content type: article

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [Database](<https://devfeed.tech/topics/database.md>), [Data structures](<https://devfeed.tech/topics/data-structures.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>), [search-engines](<https://devfeed.tech/topics/search-engines.md>)

Tags: [b-tree](<https://devfeed.tech/tags/b-tree.md>), [data-structure](<https://devfeed.tech/tags/data-structure.md>), [database](<https://devfeed.tech/tags/database.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [full-text-search](<https://devfeed.tech/tags/full-text-search.md>), [indexes](<https://devfeed.tech/tags/indexes.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [queries](<https://devfeed.tech/tags/queries.md>)

### AI overview

An explanation of how full-text search engines work, focusing on inverted indexes and their implementation in Postgres. It contrasts them with b-tree indexes and describes term dictionaries, postings lists, positional data, frequency data, and query processing.

### Source excerpt

How a full-text search engine works, and how it works in Postgres

## How PlanetScale Postgres Protects Logical Replication Slots During Cutovers

DevFeed: [How PlanetScale Postgres Protects Logical Replication Slots During Cutovers](<https://devfeed.tech/articles/blocking-cutovers-to-save-replication-slots-57450.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/how-to-make-a-replication-slot-survive-a-cutover>)

Author: Simeon Griggs

Published: 2026-09-21T00:00:00Z

Content type: tutorial

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [Replication](<https://devfeed.tech/topics/replication.md>), [Availability](<https://devfeed.tech/topics/availability.md>), [Database](<https://devfeed.tech/topics/database.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>)

Tags: [engineering](<https://devfeed.tech/tags/engineering.md>), [high-availability](<https://devfeed.tech/tags/high-availability.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [replication](<https://devfeed.tech/tags/replication.md>), [wal](<https://devfeed.tech/tags/wal.md>)

### AI overview

This article explains why Postgres cutovers must account for logical replication slots, not only whether a replica has replayed the write-ahead log. It describes how missing slot state can interrupt downstream consumers such as search indexes, analytics tools, and queues, and why PlanetScale blocks unsafe promotions.

### Source excerpt

Postgres understands high-availability architecture, but its defaults assume you don't have replication slots. This can get you into trouble in a cutover event. The combination of what Postgres can do and what PlanetScale lets you do is what keeps connected applications safe.

## The architecture of Neki

DevFeed: [The architecture of Neki](<https://devfeed.tech/articles/the-architecture-of-neki-55181.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/the-architecture-of-neki>)

Author: Harshit Gangal

Published: 2026-09-18T00:00:00Z

Content type: article

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [neki](<https://devfeed.tech/topics/neki.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [sharding](<https://devfeed.tech/topics/sharding.md>), [Scalability](<https://devfeed.tech/topics/scalability.md>), [Replication](<https://devfeed.tech/topics/replication.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>), [Process](<https://devfeed.tech/topics/process.md>), [container](<https://devfeed.tech/topics/container.md>)

Tags: [container](<https://devfeed.tech/tags/container.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [neki](<https://devfeed.tech/tags/neki.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [process](<https://devfeed.tech/tags/process.md>), [replication](<https://devfeed.tech/tags/replication.md>), [scaling](<https://devfeed.tech/tags/scaling.md>), [sharding](<https://devfeed.tech/tags/sharding.md>), [transactions](<https://devfeed.tech/tags/transactions.md>)

### AI overview

This article explains Neki, a sharding and scaling layer for PostgreSQL. It describes how Neki manages ordinary PostgreSQL instances, replication, connection pooling through Sidecars, routing, health reporting, and connection handling for statements, transactions, and session-scoped locks.

### Source excerpt

Sharded Postgres, from the team behind Vitess

## Introducing Lead: TIN-compatible full-text search for CI

DevFeed: [Introducing Lead: TIN-compatible full-text search for CI](<https://devfeed.tech/articles/introducing-lead-tin-compatible-full-text-search-for-ci-42160.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/introducing-lead>)

Author: Eric Ridge

Published: 2026-09-17T00:00:00Z

Content type: release

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [Database](<https://devfeed.tech/topics/database.md>), [SQL](<https://devfeed.tech/topics/sql.md>)

Tags: [3](<https://devfeed.tech/tags/3.md>), [acid](<https://devfeed.tech/tags/acid.md>), [ansi](<https://devfeed.tech/tags/ansi.md>), [bm25](<https://devfeed.tech/tags/bm25.md>), [ci](<https://devfeed.tech/tags/ci.md>), [concurrent](<https://devfeed.tech/tags/concurrent.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [extension](<https://devfeed.tech/tags/extension.md>), [full-text-search](<https://devfeed.tech/tags/full-text-search.md>), [html](<https://devfeed.tech/tags/html.md>), [lead](<https://devfeed.tech/tags/lead.md>), [make](<https://devfeed.tech/tags/make.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [search](<https://devfeed.tech/tags/search.md>), [sql](<https://devfeed.tech/tags/sql.md>), [staging](<https://devfeed.tech/tags/staging.md>), [tests](<https://devfeed.tech/tags/tests.md>), [tokenizers](<https://devfeed.tech/tags/tokenizers.md>), [transactions](<https://devfeed.tech/tags/transactions.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

Lead is a TIN-compatible PostgreSQL full-text search extension designed for CI, development, and staging. It preserves TIN's search features and correctness but uses full table scans, making it much slower and suitable for small test datasets rather than production workloads.

### Source excerpt

Lead is a feature-equivalent version of TIN you can run in CI

## Introducing TIN: full-text search for Postgres

DevFeed: [Introducing TIN: full-text search for Postgres](<https://devfeed.tech/articles/introducing-tin-full-text-search-for-postgres-31551.md>)

Original publisher: [Read original article](<https://planetscale.com/blog/introducing-tin>)

Author: Patrick Reynolds

Published: 2026-09-16T00:00:00Z

Content type: release

Language: en

Sources: [PlanetScale](<https://devfeed.tech/sources/blog-planetscale.md>)

Topics: [Database](<https://devfeed.tech/topics/database.md>), [Benchmark](<https://devfeed.tech/topics/benchmark.md>)

Tags: [backups](<https://devfeed.tech/tags/backups.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [bm25](<https://devfeed.tech/tags/bm25.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [full-text-search](<https://devfeed.tech/tags/full-text-search.md>), [index](<https://devfeed.tech/tags/index.md>), [performance](<https://devfeed.tech/tags/performance.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [reddit](<https://devfeed.tech/tags/reddit.md>), [replication](<https://devfeed.tech/tags/replication.md>), [search](<https://devfeed.tech/tags/search.md>), [text](<https://devfeed.tech/tags/text.md>), [wikipedia](<https://devfeed.tech/tags/wikipedia.md>)

### AI overview

PlanetScale announces TIN, a full-text search extension for Postgres and Neki databases. The article describes supported query and matching features, transaction and update behavior, and benchmark workloads and corpora used to assess performance.

### Source excerpt

TIN is a fast, full-featured, full-text search index for Postgres

[Next page](<https://devfeed.tech/sources/blog-planetscale.md?cursor=WyIyMDI2LTA5LTE2VDAwOjAwOjAwKzAwOjAwIiwgIjA4MWM4NzQ5LWMzMzItNDkxYi05NzU5LTdiZTQwYzE3NWNkNSJd>)