This is a Visual Studio Code extension to assist PostgreSQL source code developers.
It allows to investigate Node *
variables to obtain it's real type based on NodeTag
and provide some other utilities.
More info you can find in documentation for pg variables view.
While debugging you can observe variables of Node *
type with it's real type.
They appear in separate action view.
It behaves like Debug->Variables view, but no colorization (limitations of VS Code Extension framework) and automatically detects real type of Node *
variables.
Also, there are intrinsics for some types:
List
elements are displayed according their types
- Support for special members like
PlannerInfo->simple_rel_array
- array is displayed using it's length
Currently, there are 36 registered special members, but you can add your own using pgsql_hacker_helper.json configuration file.
Bitmapset
elements with total lengths are displayed:$elements$
- pseudo-member
In PostgreSQL there is pprint(Node *)
which dumps passed Node variable to stdout with pretty printing it.
Using 'Dump Node to log' option in variable context menu you also will be able to do so.
This is a configuration file for extension.
It stored inside .vscode
directory in your repository - .vscode/pgsql_hacker_helper.json
.
You can use config file to extend built-in capabilities if there is no
support for something yet.
Example json:
{
"version": 2,
"specialMembers": {
"array": [
{
"typeName": "PlannerInfo",
"memberName": "simple_rel_array",
"lengthExpression": "simple_rel_array_size"
},
{
"typeName": "RelOptInfo",
"memberName": "partexprs",
"lengthExpression": "part_scheme->partnatts"
},
{
"typeName": "GatherMergeState",
"memberName": "gm_slots",
"lengthExpression": "nreaders + 1"
}
]
},
"aliases": [
{
"alias": "PlannerRef",
"type": "PlannerInfo *"
}
]
}
In example 3 array special members - arrays will be shown with specified length,
not just pointers to arrays start.
Also, PlannerRef
- typedef for PlannerInfo *
.
For more info check configuration file documentation.
There are 2 settings:
- Log level - set minimum level of log messages in Output channel. By default -
INFO
- Files with NodeTag files - list of paths points to files that contain NodeTags. By default -
src/include/nodes/nodes.h
,src/include/nodes/nodetags.h
Known issues:
- Only tested on gdb debugger, UB for other debuggers (i.e. lldb)
- If in pointer variable was garbage, extension will not detect it and expand this variable (may be garbage)
- To get NodeTags extension reads all available NodeTag files (from settings), but these files may be not created (./configure or make not run). I assume by time of debugging start files will be created, so extension catch them and process.
- Tested only with ms-vscode.cpptools extension
Fix invalid List
behaviour with different declared type - members shown for
declared type, not List
members.
Add 137 new array special members.
Optimize extension activation performance.
Treat Plan
struct as Node variable.
Fix Bitmapset elements not shown for postgres version below 17
Add support for Bitmapset
and Relids
- show elements of set.
Add custom user type aliases for Node types in configuration
Update config file layout. Current version - 2.
Hide postgres variables view when not in debug mode.
Remove EPQState from array special members
Add T_XidList support
Add more special members.
Separate json configuration file to add your own special members.
Specifying real NodeTag in variable name if it differs from declared type. Shows in square brackets.
Setup logging infrastructure. Availability to change minimum log level.
Command and button to force refresh Pg variables view.
Setting to add custom files with NodeTags.
Only valid pointers are expanded in Pg variables view
Displaying of Node *
variables in separate view in Debug view container.
Call pprint(Node *)
on selected variable in Variables
view.
Go to Issues if you want to say something: bugs, features, etc...