Re: [survey] New "Stable" QueryId based on normalized query text

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: legrand legrand <legrand_legrand(at)hotmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [survey] New "Stable" QueryId based on normalized query text
Date: 2019-03-20 22:04:22
Message-ID: CAOBaU_atk6WMxA=ajNURThwmJ2jMyEfkE88TSkwtOfvk4gXrFA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 20, 2019 at 10:30 PM legrand legrand
<legrand_legrand(at)hotmail(dot)com> wrote:
>
> maybe this patch (with a GUC)
> https://www.postgresql.org/message-id/55E51C48.1060102@uptime.jp
> would be enough for thoses actually using a text normalization function.

The rest of thread raise quite a lot of concerns about the semantics,
the cost and the correctness of this patch. After 5 minutes checking,
it wouldn't suits your need if you use custom functions, custom types,
custom operators (say using intarray extension) or if your tables
don't have columns in the same order in every environment. And there
are probably other caveats that I didn't see;

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message legrand legrand 2019-03-20 22:10:22 Re: [survey] New "Stable" QueryId based on normalized query text
Previous Message Julien Rouhaud 2019-03-20 21:44:30 Re: [survey] New "Stable" QueryId based on normalized query text