Re: Push down time-related SQLValue functions to foreign server

From: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru>, Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>, Zhihong Yu <zyu(at)yugabyte(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Push down time-related SQLValue functions to foreign server
Date: 2022-01-18 06:02:17
Message-ID: CADkLM=fYKsBRkr3h6rQGzbRmhRPPu7wrstewXNO-rfB+M2m1Ng@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> Hmm ... not really, because for these particular functions, the
> point is exactly that we *don't* translate them to some function
> call on the remote end. We evaluate them locally and push the
> resulting constant to the far side, thus avoiding issues like
> clock skew.
>

Ah, my pattern matching brain was so excited to see a use for routine
mapping that I didn't notice that important detail.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2022-01-18 06:05:10 Re: Skipping logical replication transactions on subscriber side
Previous Message Ronan Dunklau 2022-01-18 05:46:03 Re: Proposal: More structured logging