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

From Corey Huinker
Subject Re: Push down time-related SQLValue functions to foreign server
Date
Msg-id CADkLM=ekmcVFFawkLAE0vqKWMCbxeMCSSb5Yqrs4zMVV7AzfYg@mail.gmail.com
Whole thread Raw
In response to Re: Push down time-related SQLValue functions to foreign server  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Push down time-related SQLValue functions to foreign server
List pgsql-hackers
The implementation of converting now() to CURRENT_TIMESTAMP
seems like an underdocumented kluge, too.
 
I'm very late to the party, but it seems to me that this effort is describing a small subset of what "routine mapping" seems to be for: defining function calls that can be pushed down to the foreign server, and the analogous function on the foreign side. We may want to consider implementing just enough of CREATE ROUTINE MAPPING and DROP ROUTINE MAPPING to support these specific fixed functions.

pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: TAP test to cover "EndOfLogTLI != replayTLI" case
Next
From: Peter Geoghegan
Date:
Subject: Re: Removing more vacuumlazy.c special cases, relfrozenxid optimizations