PostgreSQL Transition Tables and NamedTupleStore Internals
In PostgreSQL architecture, a NamedTupleStore represents an ephemeral named relation rather than a persistent catalog table. Officially referred to within the source code as part of the NamedTuplestoreScan mechanism, these structures exist temporarily to hold transition data during trigger execution.
Implementation Context
This mechanism is pri ...
Posted on Wed, 20 May 2026 05:26:47 +0000 by JREAM
Efficient Pagination Strategies for Complex Queries in PostgreSQL
Pagination is a standard requirement for database applications, but performance often degrades when dealing with complex queries or massive result sets. While basic pagination relies on LIMIT and OFFSET, this approach forces the database to scan and discard rows, leading to high latency on deep pages.
Problems with Standard Offset Pagination
Th ...
Posted on Tue, 12 May 2026 22:15:08 +0000 by slough
Self-Hosting Teable: PostgreSQL-Powered No-Code Database
As of March 18, the default environment configuration template has been updated to the following:
TIMEZONE=UTC
# Postgres configuration
POSTGRES_HOST=teable-db
POSTGRES_PORT=5432
POSTGRES_DB=example
POSTGRES_USER=example
POSTGRES_PASSWORD=example-password
# Backend application configuration
PUBLIC_ORIGIN=http://127.0.0.1
PRISMA_DATABASE_URL=p ...
Posted on Tue, 12 May 2026 20:26:50 +0000 by Frango
Decoding PostgreSQL’s pg_filenode.map File Structure
Understanding OID to Filenode Mapping
In a standard PostgreSQL instance, each table and index corresponds to a physical file on disk. This relationship is primarily managed through the relfilenode identifier found in the pg_class catalog. For most user-defined tables, the Object Identifier (OID) aligns directly with this filenode value.
However ...
Posted on Sat, 09 May 2026 22:44:49 +0000 by hebisr