Add pageinspect functions for inspecting GIN indexes.
Patch by me, Peter Geoghegan and Michael Paquier, reviewed by Amit Kapila.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/3a82bc6f8ab38be3ed095f1c86866900b145f0f6
Modified Files
--
contrib/pageinspec
Fix bogus comments in XLogRecordAssemble
Pointed out by Michael Paquier
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/8f5dcb56cb1877f7ed6b0f3f72cc26c4e060aa61
Modified Files
--
src/backend/access/transam/xloginsert.c |8
1 file changed, 4 i
Add a comment to regress.c explaining what it contains.
Ian Barwick
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/b10a97b819a2594c97188bac02d87b550908a692
Modified Files
--
src/test/regress/regress.c | 14 +-
1 file changed, 13 insertions(
No need to call XLogEnsureRecordSpace when the relation is unlogged.
Amit Kapila
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/622983ea6964fc55f1ad3063d3d7b8f5de8e8816
Modified Files
--
src/backend/access/gin/ginfast.c |3 ++-
1 file changed, 2 inse
Make psql's \sf and \ef honor ECHO_HIDDEN.
These commands were calling the database direct rather than calling
PSQLexec like other slash commands that needed database data.
The code is also changed not to pass the connection as a parameter to
the helper functions. It's available in a global vari
Fix an error in psql that overcounted output lines.
This error counted the first line of a cell as "extra". The effect was
to cause far too frequent invocation of the pager. In most cases this
can be worked around (for example, by using the "less" pager with the -F
flag), so don't backpatch.
Bran
Simplify API for initially hooking custom-path providers into the planner.
Instead of register_custom_path_provider and a CreateCustomScanPath
callback, let's just provide a standard function hook in set_rel_pathlist.
This is more flexible than what was previously committed, is more like the
usual
Rearrange CustomScan API.
Make it work more like FDW plans do: instead of assuming that there are
expressions in a CustomScan plan node that the core code doesn't know
about, insist that all subexpressions that need planner attention be in
a "custom_exprs" list in the Plan representation. (Of cou