On Mon, Aug 12, 2019 at 2:40 PM Jim Finnerty <jfinnert(at)amazon(dot)com> wrote:
>
> If hashing names instead of using OIDs is too expensive for some workload,
> then that workload would need to be able to turn statement hashing off. So
> it needs to be optional, just like queryId is optionally computed today.
> For many cases the extra overhead of hashing object names is small compared
> to optimization time plus execution time.
Are you suggesting a fallback to oid based queryid or to entirely
disable queryid generation?
How would that work with pg_stat_statements or similar extension?