Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
Postgres FD Implementation
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Abuhujair Javed
Postgres FD Implementation
Commits
9af6bd99
Commit
9af6bd99
authored
May 22, 1998
by
Bruce Momjian
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Move FAQ_DEV to docs directory, where it belongs.
parent
9f3d6393
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
15 additions
and
12 deletions
+15
-12
doc/FAQ_DEV
doc/FAQ_DEV
+12
-11
src/DEVELOPERS
src/DEVELOPERS
+3
-1
No files found.
src/tools
/FAQ_DEV
→
doc
/FAQ_DEV
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
...
...
src/DEVELOPERS
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.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment