Topic · 33 stories · page 1 of 2
33 stories tagged postgresql on AI Tamer, newest first.
AlloyDB Express gives developers and coding agents a 1 or 2 vCPU Postgres 18 database in seconds, scales compute to zero and has a 12-month free tier.
Postgres committer Robert Haas says LLM bug reports pushed back-patch commits up over 60% this year and pulled review time from the PostgreSQL 19 release.
A NOT IN query can lose every candidate when its exclusion set contains NULL. A small SQLite example shows why and how a correlated NOT EXISTS changes the result.
Tiger Data's 13 October post introduces pg_vectorsearch, an alpha Postgres extension with a PRISM index. The post says pgvectorscale moves to maintenance.
The release team is keeping PostgreSQL 19 RC1 on 15 October 2026, adding an RC2 on 12 November, and moving general availability from 29 October to 19 November. The roadmap still said October.
An inactive PostgreSQL replication consumer can retain write-ahead log files. Learn how to inspect slot state and choose between unbounded retention and a finite recovery window.
Committer Peter Eisentraut says 8 to 10 significant features were reverted from PostgreSQL 19 in beta. He points to LLM-assisted review finding defects faster and security work cutting review time.
Kaarel Moppel's self-funded cloud runs put PostgreSQL 19 Beta 3 and Beta 4 about 3 percent ahead of 18.6 on his OLTP tests, with pgbench inserts about 25 to 30 percent faster. It is one person's beta benchmark.
A covering PostgreSQL index can supply query columns, yet an index-only scan may still fetch table rows to check visibility. Learn when that happens and what to inspect.
PostgreSQL can change how it plans a prepared query after repeated executions. Inspect custom and generic plans when parameter values have very different row counts.
PostgreSQL prevents certain cross-row anomalies by aborting a Serializable transaction. Applications must replay the entire decision, including its reads.
A preflight SELECT cannot decide whether a concurrent insert conflicts. Design the unique key first, then let PostgreSQL arbitrate each proposed row.
PostgreSQL accepts a CHECK expression that evaluates to NULL. Make optional positive quotas explicit, and pair CHECK with NOT NULL when a value is required.
Column order changes how much of a multicolumn B-tree index PostgreSQL must scan. Match the leading columns to the conditions in your queries.
SKIP LOCKED helps competing workers claim jobs without waiting. The same behavior can make an ordinary query silently omit rows it would otherwise find.
A notification can wake a worker, while a committed table row records the work. Here is how to use both across startup and reconnects.
Compare PostgreSQL’s estimated and observed row counts before changing an index. The first useful clue is often where the counts diverge.
A row policy cannot protect tenant data if the application queries through a role that bypasses it. Check table ownership, privileged roles, and views before relying on row-level security.
Use a PostgreSQL exclusion constraint to keep active reservations for the same GPU from overlapping. Range bounds and cancellation rules make the schedule explicit.
SQLite and PostgreSQL use the same name for incompatible binary JSON formats. Transfer JSON as text and let the receiving database build its own representation.
Stored and virtual generated columns calculate the same kind of value at different times. A usage total shows how to choose between them.
PostgreSQL can coordinate workers that request the same advisory lock. The application must decide where to request it and protect work that outlives the lock.
PostgreSQL does not reclaim sequence values after a transaction aborts. That is why generated IDs can have gaps, and why business counters need a separate design.
A partial index over pending jobs helps only when PostgreSQL can tell that the query asks for rows covered by the index.
