Re: Deparsing rewritten query - Mailing list pgsql-hackers

From Julien Rouhaud
Subject Re: Deparsing rewritten query
Date
Msg-id 20220204093525.op4mr4jqied5jagb@jrouhaud
Whole thread Raw
In response to Re: Deparsing rewritten query  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: Deparsing rewritten query  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
Hi,

On Wed, Feb 02, 2022 at 07:49:41PM +0100, Pavel Stehule wrote:
>
> I checked this trivial patch, and I don't see any problem. Again I run
> check-world with success. The documentation for this feature is not
> necessary. But I am not sure about regress tests. Without any other code,
> enfosing printalias will be invisible. What do you think about the
> transformation of your extension to a new module in src/test/modules? Maybe
> it can be used for other checks in future.

I'm not opposed, but previously Tom explicitly said that he thinks this feature
is useless and is strongly opposed to making any kind of promise that the
current interface to make it possible (if get_query_def() is exposed) would be
maintained.  Adding such a test module would probably a reason to reject the
patch altogether.  I'm just hoping that this change, which is a no-op for
any legal query, is acceptable.  It can only break something if you feed wrong
data to get_query_def(), which would be my problem and not the project's
problem.



pgsql-hackers by date:

Previous
From: "houzj.fnst@fujitsu.com"
Date:
Subject: RE: row filtering for logical replication
Next
From: Sergey Dudoladov
Date:
Subject: Re: Add connection active, idle time to pg_stat_activity