We make 2 comparisions between partitioned(256 HASH) and no-partitioned(same
data volume,same table attributes) , do same "UPDATE,DELETE " .
1. with partitioned tables , the "RES" from top command memory increased
quickly to 160MB and keep stable there.
From auto_explain trace, we did sa
On Mon, Sep 05, 2022 at 12:52:14PM +, James Pang (chaolpan) wrote:
> Any idea how to print SQL plan from JDBC driver ?
You could use "explain execute" on the client, or autoexplain on the
server-side.
--
Justin
PG V13, yes JDBC use prepared statements , from psql use pruned ,but even all
partitions it NOT consumes too much memory. Any idea how to print SQL plan
from JDBC driver ?
-Original Message-
From: Justin Pryzby
Sent: Monday, September 5, 2022 8:47 PM
To: James Pang (chaolpan)
Cc: p
On Mon, Sep 05, 2022 at 12:40:46PM +, James Pang (chaolpan) wrote:
> We run same update or delete SQL statement " DELETE FROM ... WHERE ... "
> the table is a hash partition table (256 hash partitions). When run the sql
> from Postgresql JDBC driver, it soon increased to 150MB memory (RES
We run same update or delete SQL statement " DELETE FROM ... WHERE ... " the
table is a hash partition table (256 hash partitions). When run the sql from
Postgresql JDBC driver, it soon increased to 150MB memory (RES filed from top
command), but when run the same SQL from psql , it only
