How about separating count query from update statement.
I found a bit performance improvement from your example.
with 10 rows, fastest time in 10 times try
yours: 989.679 ms
mine: 719.739 ms
query
---
(same DDL, DML)
WITH cnt AS (
SELECT
count(CASE WHEN tab1.a >= 60 THEN 1 EN
Hi,
I'd like to know, per column, how many values were changed by my query.
I have a working example, but i am curious what you people think about it.
Is it efficient? I have to make a self join, but i don't see a faster way.
Here's the example:
-
drop table if exists tab1 ;
create t
