Re: Push down time-related SQLValue functions to foreign server - Mailing list pgsql-hackers

From Alexander Pyhalov
Subject Re: Push down time-related SQLValue functions to foreign server
Date
Msg-id e24c6093a0e248d4d2eaf19b04d207d5@postgrespro.ru
Whole thread Raw
In response to Re: Push down time-related SQLValue functions to foreign server  (Ranier Vilela <ranier.vf@gmail.com>)
Responses Re: Push down time-related SQLValue functions to foreign server  (Ranier Vilela <ranier.vf@gmail.com>)
Re: Push down time-related SQLValue functions to foreign server  (Zhihong Yu <zyu@yugabyte.com>)
Re: Push down time-related SQLValue functions to foreign server  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hi.

Ranier Vilela писал 2021-08-19 14:01:
> Em qui., 19 de ago. de 2021 às 07:50, Zhihong Yu <zyu@yugabyte.com>
>> Hi,
>> For 0001 patch:
>> 
>> +               if ((s->op != SVFOP_CURRENT_TIMESTAMP) &&
>> +                   (s->op != SVFOP_CURRENT_TIMESTAMP_N) &&
>> +                   (s->op != SVFOP_CURRENT_TIME) &&
>> ...
>> 
>> The above check appears more than once. If extracted into a helper
>> method, it would help reduce duplicate and make the code more
>> readable.
> 
> Perhaps in a MACRO?

Changed this check to a macro, also fixed condition in 
is_foreign_param() and added test for it.
Also fixed comment in prepare_query_params().


-- 
Best regards,
Alexander Pyhalov,
Postgres Professional
Attachment

pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: pg_veryfybackup can fail with a valid backup for TLI > 1
Next
From: Michael Paquier
Date:
Subject: Re: pg_veryfybackup can fail with a valid backup for TLI > 1