timescaledb icon indicating copy to clipboard operation
timescaledb copied to clipboard

Support unlogged hypertable/chunks

Open Dr-Steve opened this issue 6 years ago • 3 comments

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.

Dr-Steve avatar Nov 02 '18 19:11 Dr-Steve

Really hoping this happens!

s-ilyas avatar Mar 03 '20 14:03 s-ilyas

+1

Alexander3 avatar Jul 06 '22 11:07 Alexander3

+1

tjcutajar avatar Jul 29 '22 15:07 tjcutajar

+1

tminglei avatar Sep 22 '22 13:09 tminglei

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.

haydenflinner avatar Oct 08 '22 18:10 haydenflinner

+1

ErezLevip avatar Nov 10 '22 08:11 ErezLevip

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

Alexander3 avatar Jan 30 '23 12:01 Alexander3

look forward to this feature

jsvisa avatar Feb 23 '23 02:02 jsvisa

+1

kgreav avatar Sep 17 '23 01:09 kgreav

+1. Very useful for some of our tables.

mbtx2 avatar Oct 09 '23 17:10 mbtx2

+1 we very need this

tadasgedgaudas avatar Nov 21 '23 10:11 tadasgedgaudas