Sebastian Utz
Sebastian Utz
@Lyra126 Ok thank you for trying, I'll close this then.
After asking more about the problem this should solve, I got this additional information: > The problem is mainly around accounting cross-container traffic vs to the outside world - we...
@SStorm @proddata For your current use-case, is it enough to expose the traffic statistics via JMX?
I think, that only - LDAP authentication (listed as 1) - LDAP authorization (listed as 3) of the described Level of LDAP integrations are relevant for us to support a...
@vamsikrishnacse Your are right, the optimization can be also achieved by adding the filter directly to the query. I'd slightly favor my initial query as it would replace the relation...
@sayyidhussain Sure, thanks!
> While the feature request to include separate schema and table names might make it easier to work with other tables, I still consider the current behaviour in the tables...
I've added another possible solution to use CREATE TABLE + SWAP TABLE (drop_source = true) (thx @jeeminso for coming up with this idea). After an internal discussion, this would be...
> Implementation deviates from PostgreSQL. PostgreSQL always returns NUMERIC for round(). What is the reason for this deviation?
It's currently not completely clear what is missing in our planner to support any join order algorithm, like do our existing join operators (join pairs) have enough information declared, etc....