Support unlogged hypertable/chunks

[Dr-Steve]

I use timescale for an insert intensive use case that does not require the data integrity that the WAL Logs offer. It would increase my performance to be able to turn off logging entirely. This is currently not supported by timescale.

[s-ilyas]

Really hoping this happens!

[Alexander3]

+1

[tjcutajar]

+1

[tminglei]

+1

[haydenflinner]

I was counting on this to work to justify using timescale as my starting point over the smaller, faster time-series specific DBs. Figured I'd be able to trade some safety in for performance.

I don't guess there's a workaround right? Like somehow disabling timescale and switching to unlogged before my batch inserts, then putting it back with timescale to get the nice aging out of chunks + columnar compression.

[ErezLevip]

+1

[Alexander3]

@svenklemm Why hypertables actually need table to be LOGGED ? Are we using WAL somehow?

[jsvisa]

look forward to this feature

[kgreav]

+1

[mbtx2]

+1. Very useful for some of our tables.

[tadasgedgaudas]

+1 we very need this