This answer motivated think again my following tables but I am still uncertain how to store variables/results from data analysis for quick selection in post-processing.
If stored, I think it is well ...
Our system writes a lots of data (kind of Big Data system). Write performance is good enough for our needs but read performance is really too slow.
The primary key (constraint) structure is similar ...
I have a legacy schema (disclaimer!) that uses a hash-based generated id for the primary key for all tables (there are many). An example of such an id is:
VACUUM usually does not return disk space to operating system, except in some special cases.
From the docs:
The standard form of VACUUM removes dead row versions in tables and indexes and marks the ...
I have 400 million rows in a Postgres db, and the table has 18 columns:
id serial NOT NULL,
e timestamp without time zone,
g timestamp without ...
I have heavily updated / accessed table where I store serialized java objects. They are in the table for 2-3 hours (also are being updated during that period) and then removed. Size of table is around ...