Closed df7cb closed 1 year ago
We can't trivially drop stringToQualifiedNameList
since it does additional processing of the string. It might be possible to do it, but I tried and got some regression diffs in disable_hashagg.sql. Possibly just a matter of switching representations of the same thing, but I don't have time to investigate that now.
Perhaps merge this first and worry about that optimization in a followup PR?
Yes, I can see the regress failures. Looks like we need to use stringToQualifiedNameList
.
@df7cb Are you able to merge? Or should I do it?
Hello, when could we expect this patch to be merged? Thanks!
PG16 ships its own get_extension_schema function, use that. stringToQualifiedNameList grew and extra argument for error reporting that can be set to NULL.
Close #146.