Accept pg_upgraded tuples during multixact freezing
The new MultiXact freezing routines introduced by commit 8e9a16ab8f7
neglected to consider tuples that came from a pg_upgrade'd database; a
vacuum run that tried to freeze such tuples would die with an error such
as
ERROR: MultiXactId 11415437 do
Accept pg_upgraded tuples during multixact freezing
The new MultiXact freezing routines introduced by commit 8e9a16ab8f7
neglected to consider tuples that came from a pg_upgrade'd database; a
vacuum run that tried to freeze such tuples would die with an error such
as
ERROR: MultiXactId 11415437 do
Move username lookup functions from /port to /common
Per suggestion from Peter E and Alvaro
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/111022eac64579cc12d20e33146ce01717562b29
Modified Files
--
src/backend/libpq/auth.c |1 +
src/backend/main
Adjust pg_upgrade for move of username lookup functions to /common
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/850ade3e32ea12e0c6b2d10c6b628772bf851727
Modified Files
--
contrib/pg_upgrade/util.c |1 +
1 file changed, 1 insertion(+)
--
Sent via
Remove DESCR entries for json operator functions.
Per -hackers discussion.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/11829ff8b2c877469845c08e5966a704b814ca5f
Modified Files
--
src/include/catalog/pg_proc.h |6 --
1 file changed, 6 deletions(
Add another regression test cross-checking operator and function comments.
Add a query that lists all the functions that are operator implementation
functions and have a SQL comment that doesn't just say "implementation of
XYZ operator". (Note that the preceding test checks that such functions'
c