R: Slow performance updating CLOB data

From: Nicola Zanaga <NZanaga(at)efsw(dot)it>
To: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>, Thomas Kellerer <spam_eater(at)gmx(dot)net>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org>
Subject: R: Slow performance updating CLOB data
Date: 2016-07-18 10:27:20
Message-ID: 47856758BAE4794A9EC4FCA2E63FC85E3705944D@exchange.intranet.efsw.it
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Thanks for the quick replies.

I'm using updateable resultset only to update CLOB data.
My application uses many databases. This method can be used with many driver (I think this is the "standard" mode to update CLOB data).

I took a look at the code in PgResultSet, and I think the driver will be slow with any operation on updateable resultset, because it will always call " isUpdateable()" to do any operation.
So, in my opinion, this makes updateable resultset quite useless

To check if the query is updateable, the code first checks if it's using a single table, so should be easy to cache table and primary keys.

-----Messaggio originale-----
Da: pgsql-jdbc-owner(at)postgresql(dot)org [mailto:pgsql-jdbc-owner(at)postgresql(dot)org] Per conto di Vladimir Sitnikov
Inviato: lunedì 18 luglio 2016 10:54
A: Thomas Kellerer; pgsql-jdbc(at)postgresql(dot)org
Oggetto: Re: [JDBC] Slow performance updating CLOB data

‎Is there a reason of using updateable resultset?
Simple update table set... should work just fine.

PS. Having table -> PK cache in pgjdbc would be good.

‎Vladimir

--
Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org) To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Dave Cramer 2016-07-18 10:34:20 Re: Slow performance updating CLOB data
Previous Message Vladimir Sitnikov 2016-07-18 08:53:49 Re: Slow performance updating CLOB data