Re: Cache lookup errors with functions manipulation object addresses
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>, pgsql-hackers@lists.postgresql.org
Date: 2019-01-31T07:08:18Z
Lists: pgsql-hackers
Attachments
- 0001-Add-flag-to-format_type_extended-to-enforce-NULL-nes.patch (text/x-diff) patch 0001
- 0002-Refactor-format-procedure-and-operator-APIs-to-be-mo.patch (text/x-diff) patch 0002
- 0003-Eliminate-user-visible-cache-lookup-errors-for-objad.patch (text/x-diff) patch 0003
On Tue, Dec 25, 2018 at 01:34:38PM +0900, Michael Paquier wrote: > With that all the regression tests show a consistent behavior for all > object types when those are undefined. Thoughts? End-of-commit-fest rebase and moved to next CF. -- Michael
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