Re: [survey] New "Stable" QueryId based on normalized query text - Mailing list pgsql-hackers

From Jim Finnerty
Subject Re: [survey] New "Stable" QueryId based on normalized query text
Date
Msg-id 1565613624729-0.post@n3.nabble.com
Whole thread Raw
In response to Re: [survey] New "Stable" QueryId based on normalized query text  (Julien Rouhaud <rjuju123@gmail.com>)
Responses Re: [survey] New "Stable" QueryId based on normalized query text  (Julien Rouhaud <rjuju123@gmail.com>)
List pgsql-hackers
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.



-----
Jim Finnerty, AWS, Amazon Aurora PostgreSQL
--
Sent from: https://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: block-level incremental backup
Next
From: Evgeniy Efimkin
Date:
Subject: Re: [survey] New "Stable" QueryId based on normalized query text