Re: Fast insertion indexes: why no developments

Jeff Janes wrote
> Are partitions read-only once time has moved on, or can stragglers show up
> that need to be inserted into older partitions?
>
> You could periodically merge older partitions into larger tables, index
> those aggregated tables, then transactionally disinherit the old
> partitions
> and inherit the new aggregated one. This would keep the value of K down,
> at the expense of re-writing data multiple times (but all method write
> data
> multiple times, some just hide it from you).

Yes, we could "merge" the partitions: the idea was to merge them during
night hour, when traffic is low ( and NSA people are sleeping ;) )

Jeff Janes wrote
> By the way, what is the transaction structure of your inserts? Are they
> large batches between commits, or is each row committed?

Of course large batches (using COPY)

--
View this message in context: http://postgresql.1045698.n5.nabble.com/Fast-insertion-indexes-why-no-developments-tp5776227p5776416.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.