Patrick Decat

So FWIW, I've updated my alerting automation to ignore this specific E32 error code.

I believe E32 just means heating is requested, but the heater element isn't actually on because target temperature is already reached.

Thanks OP for the example! I've adapted it a bit to work for Lambda layers: ``` module "lambda_layer" { source = "terraform-aws-modules/lambda/aws" version = "8.0.1" create_layer = true layer_name =...

Does it work on second apply?

Hi @pskrbasu, I may have uncovered some further things to adjust with PostgreSQL 17+, as some queries which were working with PostgreSQL 14.17 (Steampipe's embedded) and PostgreSQL 15.13 (FDW standalone)...

I've reproduced the issue with PostgreSQL 16.9 with `298` instead of `315` (still `T_RestrictInfo`): ``` ERROR: XX000: unrecognized node type: 298 LOCATION: expression_tree_walker_impl, nodeFuncs.c:2539 STATEMENT: SELECT ``` ``` grep 298...

Searching for `"unrecognized node type" "RestrictInfo"`, I found this: > RestrictInfo is not a general expression node and support for it has been deliberately omitted from expression_tree_walker(). So I think...

It also happens without JSON columns involved, e.g. here's the smallest reproduction case I could come with so far: ``` ERROR: XX000: unrecognized node type: 315 LOCATION: expression_tree_walker_impl, nodeFuncs.c:2660 STATEMENT:...

So, I've finally managed to eliminate the `unrecognized node type: 315` errors using the [extract_actual_clauses](https://doxygen.postgresql.org/restrictinfo_8c_source.html#l00485) which strips those RestrictInfo nodes: ``` /* * extract_actual_clauses * * Extract bare clauses from...

Hmm, also getting the following error with some other queries: ``` 2025-07-21 21:25:29.333 UTC [221671] ERROR: XX000: unrecognized node type: 318 2025-07-21 21:25:29.333 UTC [221671] CONTEXT: SQL statement "SELECT 'APPLICATION_GATEWAY'...