| From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
|---|---|
| To: | Dave Cramer <pg(at)fastcrypt(dot)com>, Nicola Zanaga <NZanaga(at)efsw(dot)it> |
| Cc: | Thomas Kellerer <spam_eater(at)gmx(dot)net>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Slow performance updating CLOB data |
| Date: | 2016-07-18 11:48:09 |
| Message-ID: | CAB=Je-EGvjnG1YjoMpxk6OF1vE2CEQjsPp1UXHq2sM=r=wrkJg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nicola Zanaga | 2016-07-18 12:28:52 | R: Slow performance updating CLOB data |
| Previous Message | Dave Cramer | 2016-07-18 10:34:20 | Re: Slow performance updating CLOB data |