中文 English Français Русский Español العربية

Chris van Eijk: stack depth limit exceeded in PostgreSQL: four causes

Planet PostgreSQL2026-10-16 08:000 views

What raised 'stack depth limit exceeded' in PostgreSQL 17, measured: triggers, recursion, a policy reading its table via a function, long expressions.

Source：https://postgr.es/p/9yL

My favorites

PreviousChris van Eijk: Rails, ActiveRecord and PostgreSQL RLS, measured NextShow HN: Turn a prompt into a hardware project you can wire up and flash

The Scariest Part of "Skynet Mode" Is Your Own Unauthenticated Endpoint

Somebody finally caught an attack agent with its pants down, and the interesting part isn't the name. Symantec researche

0dev.to Security

pgvector for Beginners: Add Semantic Search to PostgreSQL

You already have PostgreSQL, backups, and a team that knows how to operate them. Then a new feature asks for semantic se

0dev.to

Vibhor Kumar: Autonomous Postgres at PGConf.EU 2026: From Scripts to Self-Driving, and the Primitives in Between

A morning in Valencia On Friday, 23 October 2026, the last day of PGConf.EU in Valencia, almost 40 practitioners, builde

0Planet PostgreSQL

From one command to a live app on a $5 VPS

You own the server, the code and the data. Here is what the first ten minutes look like. Why the default path gets annoy

0dev.to

Database Transaction là gì? Phân biệt Transaction và SQL thông thường

Mục tiêu: Hiểu bản chất Transaction, ACID, COMMIT, ROLLBACK và các câu hỏi thường gặp khi phỏng vấn Backend/DevOps. 1. T

0dev.to Database

Choose a database by access pattern, not by hype

Across ten years of backend work I've shipped production systems on MySQL, PostgreSQL, DynamoDB, MongoDB, Elasticsearch,