Re: Slow performance updating CLOB data - Mailing list pgsql-jdbc

From Vladimir Sitnikov
Subject Re: Slow performance updating CLOB data
Date
Msg-id CAB=Je-EGvjnG1YjoMpxk6OF1vE2CEQjsPp1UXHq2sM=r=wrkJg@mail.gmail.com
Whole thread Raw
In response to Re: Slow performance updating CLOB data  (Dave Cramer <pg@fastcrypt.com>)
Responses R: Slow performance updating CLOB data  (Nicola Zanaga <NZanaga@efsw.it>)
Re: Slow performance updating CLOB data  (Dave Cramer <pg@fastcrypt.com>)
List pgsql-jdbc
Dave>Well all drivers have to do something similar. Not all result sets are updatable. What do other drivers do ?

Technically speaking, pgjdbc could cache the names of primary keys for a given table.
It would be useful at least in two places:
1) updateable resultset
2) return generated keys

However, as of now no such cache exists in pgjdbc.
The second issue is the backend does not send notifications on DDL changes. Thus the cache can easily get out of sync when java thinks there's a column named A, and in reality the column was dropped long ago.

Vladimir

pgsql-jdbc by date:

Previous
From: Dave Cramer
Date:
Subject: Re: Slow performance updating CLOB data
Next
From: Nicola Zanaga
Date:
Subject: R: Slow performance updating CLOB data