Re: Multiple Query IDs for a rewritten parse tree - Mailing list pgsql-hackers

From Julien Rouhaud
Subject Re: Multiple Query IDs for a rewritten parse tree
Date
Msg-id 20220109120444.gxtnavdswou2g3wa@jrouhaud
Whole thread Raw
In response to Re: Multiple Query IDs for a rewritten parse tree  (Dmitry Dolgov <9erthalion6@gmail.com>)
List pgsql-hackers
On Sun, Jan 09, 2022 at 12:43:06PM +0100, Dmitry Dolgov wrote:
>
> An extension that wants a slightly modified version of hash calculation
> implementation from the core would still need to copy everything. The
> core probably has to provide more than one (hash, method) pair to cover
> some basic needs.

Or just GUC(s) to adapt the behavior.  But in any case there isn't much that
can be done that won't result in a huge performance drop (like e.g. the wanted
stability over logical replication or backup/restore).



pgsql-hackers by date:

Previous
From: Dmitry Dolgov
Date:
Subject: Re: Multiple Query IDs for a rewritten parse tree
Next
From: Julien Rouhaud
Date:
Subject: Re: Multiple Query IDs for a rewritten parse tree