Koskamo
Navigation

PostgreSQL best practices

Source-linked guidance on PostgreSQL fundamentals: EXPLAIN query plans, index types, transaction isolation, table constraints, and routine vacuuming. Scoped to the current PostgreSQL documentation; not a version-specific tuning corpus.

Browse 5 documentsUse with your agent

Documents

Showing 1–5 of 5 documents

DocumentVersion

Index types and when the planner uses them

PostgreSQL provides several index types: B-tree, Hash, GiST, SP-GiST, GIN, BRIN, and the extension bloom. Each index type uses a different algorithm best suited to different…

v1

Reading query plans with EXPLAIN

PostgreSQL devises a query plan for each query it receives, and the EXPLAIN command shows what query plan the planner creates for any query. Plan costs are measured in arbitrary…

v1

Routine VACUUM and up-to-date planner statistics

PostgreSQL's VACUUM command has to process each table on a regular basis for several reasons: to recover or reuse disk space occupied by updated or deleted rows, to update data…

v1

Table constraints as the guardian of data integrity

SQL lets you define constraints on columns and tables, and constraints give you as much control over the data in your tables as you wish: if a user attempts to store data in a…

v1

Transaction isolation levels under concurrency

The SQL standard defines four levels of transaction isolation; the most strict is Serializable, and the other three are defined in terms of phenomena resulting from interaction…

v1

Source, review, and usage
Published on Koskamo by
Koskamo editorial
Version
1
Documents
5 documents
Reviewed
2026-10-04
Agent lookups
0 in the last 90 days
Reuse
Original summaries; linked sources retain their own terms.
Review status
Maintained with the application; source links supplied

Original sources are linked on each document. Owner approval records a publishing decision; it does not imply independent fact checking.

Use this dataset from an agent

Agents can query it without an account. POST to /api/v1/retrieve, or connect an MCP client and call koskamo_retrieve with dataset: "postgres-best-practices".

Set up your agentRead documents as JSON

The JSON endpoint returns document text and source links in pages. Use limit and offset to retrieve more records; total gives the dataset size.

retrieve request
curl --fail-with-body 'https://koskamo.com/api/v1/retrieve' -H 'Content-Type: application/json' --data-raw '{"query":"postgres-best-practices","dataset":"postgres-best-practices","top_k":3}'

Change history

This dataset is maintained with the application. Its history is the Koskamo release history; the review date above is when its sources were last checked.