Re: Cache lookup errors with functions manipulation object addresses
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Aleksander Alekseev <a.alekseev@postgrespro.ru>, pgsql-hackers@lists.postgresql.org
Date: 2018-05-14T22:32:52Z
Lists: pgsql-hackers
On 2018-May-15, Michael Paquier wrote: > On Mon, May 14, 2018 at 04:27:48PM -0400, Alvaro Herrera wrote: > > I think we're better off adding a new function and avoid changing the > > signature of GetForeignServer et al. Or maybe rename the function and > > keep the original name as a compatibility wrapper macro. > > On the other hand, if we make the change visible because of a > compilation failures, then modules would become aware of the problem and > react? Presumably, if you invoke a FDW and its handler finds that the ForeignServer doesn't exist, what is it to do other than raise an error? I can't see that there's any possible improvement. So, I don't know -- if the reaction is to add a #ifdef for pg version that adds a second argument passed always false, then we haven't won anything. > I would not expect modules to set missing_ok to true anyway as they > expect those objects to exist, so I can live with a new function. Exactly. > What about naming those GetForeignServerExtended and > GetForeignDataWrapperExtended? WFM. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Eliminate cache lookup errors in SQL functions for object addresses
- 2a10fdc4307a 14.0 landed
-
Refactor routines for name lookups of procedures and operators
- aa38434824c4 14.0 landed
-
Add new flag to format_type_extended() to get NULL for undefined type
- 1185c782943c 14.0 landed
-
Introduce new extended routines for FDW and foreign server lookups
- 8fb569e978af 12.0 landed
-
Refactor routines for subscription and publication lookups
- 1d6fbc38d9ed 12.0 landed
-
get_relid_attribute_name is dead, long live get_attname
- 8237f27b504f 11.0 landed
-
Tweak parser so that there is a defined representation for datatypes
- a585c20d12d0 7.2.1 cited