On Mon, Aug 26, 2019 at 4:29 PM Arcadiy Ivanov wrote:
> This problem is not limited to IoT but to RT financial transaction
> ingestion as well.
Not surprising, since the TPC-E benchmark models a financial trading
application. Perhaps it exhibits this behavior because it is actually
representative
On Mon, Aug 26, 2019 at 4:59 PM Arcadiy Ivanov wrote:
> But apart from TPC-E and having to perform to it, is there any practical
> real world usefulness in trying to have a B-tree index on TS-based data
> just to have a PK on it, as opposed to having a BRIN on a TS field and
> calling it a day?
T
On 8/26/19 6:48 PM, Peter Geoghegan wrote:
Such data often consists of timestamps from a large number
of low cost devices -- event data that arrives *approximately* in
order. This is more or less the problem that the TimescaleDB extension
targets, so it seems likely that a fair number of users ca
On 8/26/19 7:49 PM, Peter Geoghegan wrote:
Not surprising, since the TPC-E benchmark models a financial trading
application.
The good news there is that that will almost certainly be a lot better
in Postgres 12. TPC-E also has a number of very low cardinality
indexes, despite being an OLTP ben
The well known rightmost page split optimization (where we apply leaf
page fill factor) usually does a great job of maximizing space
utilization with indexes on a single auto-incrementing column or
timestamp column, by packing the left half of the rightmost page full.
Splitting the rightmost page p
