Bharathy

Issue: ===== Consider below example table: CREATE TABLE sample_table ( cpu double precision null, time TIMESTAMP WITH TIME ZONE NOT NULL, sensor_id INTEGER NOT NULL, name TEXT default 'this is...

Below is the explanation for what is happening. Consider this example: ----------------------- ``` DROP TABLE foo_ts; CREATE TABLE foo_ts ( tm timestamp with time zone, c1 integer default 1234, c2...

Hi Justin, Consider simple table like below: ``` CREATE TABLE foo_ts ( tm timestamp with time zone, c1 integer default 1234, c2 char(10) default 'char(10)', c3 varchar(30) default 'varchar(30)', c4...

Hi Justin, You seem to have a valid proposal. Reporting a warning and documenting the limits for compressed hypertable can be done. Will come up with a solution. Thanks.

Hi @phemmer, I tried to reproduce on TimescaleDB 2.9.0 with PG14 and could not see major difference in before_compression* numbers. Please see below the details. Let me know if iam...

Hi @phemmer, A gentle reminder to let me know if the issue still exists. Else i would like to close the issue.

Hi @jvanns, I try to repeat the same steps which you shared in dbfiddle. Unfortunately i could not reproduce or i dont understand where the problem lies. Can you please...

Hi @jvanns, Please see below what i understand from your recent comments and tell me if iam correct. ``` tsdb=# tsdb=# CREATE TABLE regular( tsdb(# id INT NOT NULL, tsdb(#...

The issue is in the below subplan when executing Bitmap Heap Scan Node. ``` -> Custom Scan (DecompressChunk) on _hyper_71_12586_chunk (cost=4.44..4.44 rows=1000 width=12) Filter: ((metrics_temp."time" = "time") AND (metrics_temp.device_id =...

Refer #5252 Will close this issue once 5252 is merged to main branch.