Re: Patch to fix bug #6293 - regression in driver performance with regards to ResultSetMetaData-heavy workloads
От
Kris Jurka
Тема
Re: Patch to fix bug #6293 - regression in driver performance
with regards to ResultSetMetaData-heavy workloads
Дата
Msg-id
alpine.BSO.2.00.1202100407320.8161@leary.csoft.net
Ответ на
Re: Patch to fix bug #6293 - regression in driver performance with regards to ResultSetMetaData-heavy workloads (Steven Schlansker)
Список
Дерево обсуждения
Patch to fix bug #6293 - regression in driver performance with regards to ResultSetMetaData-heavy workloads Steven Schlansker <steven@likeness.com>
Re: Patch to fix bug #6293 - regression in driver performance
with regards to ResultSetMetaData-heavy workloads Dave Cramer <pg@fastcrypt.com>
Re: Patch to fix bug #6293 - regression in driver performance with regards to ResultSetMetaData-heavy workloads Steven Schlansker <steven@likeness.com>
Re: Patch to fix bug #6293 - regression in driver performance with regards to ResultSetMetaData-heavy workloads Steven Schlansker <stevenschlansker@gmail.com>
Re: Patch to fix bug #6293 - regression in driver performance
with regards to ResultSetMetaData-heavy workloads Kris Jurka <books@ejurka.com>
On Thu, 9 Feb 2012, Steven Schlansker wrote: > So IMO whether getMetaData() is thread safe or not is irrelevant, as > nothing else in the class is. Making the entire class thread safe would > probably not be worth the effort (sharing a ResultSet between threads > just sounds like a bad idea, and the increased synchronization overhead > would punish everyone who does it "right") I concur that thread safety is not an issue here. I have committed a variant of your fix that moves the caching into AbstractJdbc2ResultSet instead of having each concrete implementation class have its own copy of that code. Kris Jurka
В списке pgsql-jdbc по дате отправления
От: Steven Schlansker
Дата: