Álvaro Hernández Tortosa

I agree it might be difficult to implement in a columnar store. However, and while the general append-only use case is good enough, there might be a wider audience out...

The problem is that those that need this, occasionally, but sometimes, may not use cstore_fdw at all since it would not be supported. So implementing it may widen the user...

That's really cool @sriharsha9992 Is that code submitted as a PR? @mtuncer I'm subscribed now to the cstore-users group and I'll be happy to provide feedback on future directions when...

> I think the eks join command being referred to here is the snap provided cli. Yes, exactly. You can see how it was called here: https://gitlab.com/ongresinc/blog-posts-src/-/blob/master/202012-firecracker_cloud_image_automation/ansible/roles/eks_node/tasks/01-join_master.yaml

@vlsi Code duplication improvements should be significant. Current code uses a "strategy" consisting on class fields and methods which essentially do the same for both queries and portals. This has...

> @ahachete , I see there is a good point to abstract `Cleaner` pattern. > However, > > 1. `ServerResourcesCleaner#processDeadParsedObjects sendCloseStatementClearReference` does look too tightly coupled to the specific case....

> > However, when you say previous code had a single field, in reality is not true: it had three, but they were in the QueryExecutorImpl class (parsedQueryMap, parsedQueryCleanupQueue and...

Hey there! What should we do with this PR @vlsi @davecramer ?

Main value was certainly to support GraalVM. Good news it is supported now anyway. However, IMHO this patch made the code much clearer and removed the contrived use of PhantomReferences...

May I suggest an ANTLR4 grammar?