Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
9af6bd99
Commit
9af6bd99
authored
26 years ago
by
Bruce Momjian
Browse files
Options
Downloads
Patches
Plain Diff
Move FAQ_DEV to docs directory, where it belongs.
parent
9f3d6393
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/FAQ_DEV
+12
-11
12 additions, 11 deletions
doc/FAQ_DEV
src/DEVELOPERS
+3
-1
3 additions, 1 deletion
src/DEVELOPERS
with
15 additions
and
12 deletions
src/tools
/FAQ_DEV
→
doc
/FAQ_DEV
+
12
−
11
View file @
9af6bd99
...
...
@@ -23,9 +23,9 @@ Questions answered:
1) What tools are available for developers?
Aside from the User documentation mentioned in the regular FAQ, there
are
several development tools available. First, all the files in the
/tools
directory are designed for developers.
Aside from the User documentation mentioned in the regular FAQ, there
are
several development tools available. First, all the files in the
pgsql/src/tools
directory are designed for developers.
RELEASE_CHANGES changes we have to make for each release
SQL_keywords standard SQL'92 keywords
...
...
@@ -42,14 +42,15 @@ directory are designed for developers.
mkldexport create AIX exports file
pgindent indents C source files
Let me note some of these. If you point your browser at the tools/backend
directory, you will see all the backend components in a flow chart. You can
click on any one to see a description. If you then click on the directory
name, you will be taken to the source directory, to browse the actual source
code behind it. We also have several README files in some source directories
to describe the function of the module. The browser will display these when
you enter the directory also. The tools/backend directory is also contained
on our web page under the title Backend Flowchart.
Let me note some of these. If you point your browser at the
pgsql/src/tools/backend directory, you will see all the backend
components in a flow chart. You can click on any one to see a
description. If you then click on the directory name, you will be taken
to the source directory, to browse the actual source code behind it. We
also have several README files in some source directories to describe
the function of the module. The browser will display these when you
enter the directory also. The pgsql/src/tools/backend directory is also
contained on our web page under the title Backend Flowchart.
Second, you really should have an editor that can handle tags, so you can
tag a function call to see the function definition, and then tag inside that
...
...
This diff is collapsed.
Click to expand it.
src/DEVELOPERS
+
3
−
1
View file @
9af6bd99
All the developer tools are located in the /tools directory.
Read the Developer's FAQ in pgsql/doc/FAQ_DEV. All the developer tools
are located in the pgsql/src/tools directory.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment