Richard Chien

Recently a user asked about the following use case: ```sql create table raw_data ( ts timestamp, foo int, bar int ); insert into raw_data values (now(), null, 1); insert into...

The panic is the surface problem. The deep problem is that `Date t::date` will try to parse `t` as `date` type, so that the final schema is actually completely not...

> Here the `interval '1 month'` is actually of variable length (28 to 31 days). @stdrc Could you confirm if such "bad" interval values would be problematic in the intended...

> FYI the following "worse" interval value can cause an infinite loop in PostgreSQL batch query: > > ``` > select generate_series('2024-01-31T00:00:00Z'::timestamptz, now(), interval '1 month -29 days'); > ```...

Because the watermark definition on the source table is `WATERMARK FOR "requestedAt" AS "requestedAt" - INTERVAL '5 SECONDS'`, the latest data row `07:06:24.452+00:00` can only cause a watermark of `07:01:24.452+00:00`...

直接提 pr 吧

Could you plz give some example? Previously we have a bug related to this (https://github.com/risingwavelabs/risingwave/issues/13653), at that time we fixed OverWindow predicate pushdown in a kinda conservative way.

Here's an example that explains why this optimization won't work: ``` x | ord ---|----- 8 | 1 7 | 2 4 | 3 5 | 4 ``` ```sql select...

> ``` > LAG(md.data) OVER (PARTITION BY md.meterId ORDER BY md.datatime) AS prev_power, > LAG(md.data, 2) OVER (PARTITION BY md.meterId ORDER BY md.datatime) AS prev_power_2, > LAG(md.data, 3) OVER (PARTITION...

> ``` > rw-main risingwave_storage::hummock::event_handler::hummock_event_handler: cannot acquire lock for all read version pending_count=1 total_count=192 > ``` > > > > > > > i found many log like this, what...