lidavidm commented on issue #1755: URL: https://github.com/apache/arrow-adbc/issues/1755#issuecomment-4204476389
@Mandukhai-Alimaa are you interested in looking at this? I think there are a few questions in play: - Is it safe to hardcode the a list of "base" OIDs so that we don't have to do this lookup at the start? (We'd need to confirm that they're stable across PostgreSQL versions, and whether forks/PostgreSQL-compatible databases use the same OIDs or not. I know Redshift does _not_ use the same OIDs, but I want us to drop Redshift support anyways: https://github.com/apache/arrow-adbc/issues/4151) - Can we replicate the issue if we set up Postgres with a ton of OIDs? - Can we replicate/figure out if we're accidentally double-initializing something in the Python bindings that would cause this apparent doubling of initialization time? If we can replicate it, then we can consider lazily caching or something else to mitigate it (or ideally, just hardcoding OIDs, at least for Postgres itself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
