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
4aa09c57
Commit
4aa09c57
authored
20 years ago
by
Bruce Momjian
Browse files
Options
Downloads
Patches
Plain Diff
Typo fixes.
parent
e5615c42
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/src/sgml/external-projects.sgml
+13
-17
13 additions, 17 deletions
doc/src/sgml/external-projects.sgml
with
13 additions
and
17 deletions
doc/src/sgml/external-projects.sgml
+
13
−
17
View file @
4aa09c57
<!--
$PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.
3
2004/12/03 06:
18:12
momjian Exp $
$PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.
4
2004/12/03 06:
30:40
momjian Exp $
-->
<chapter id="external-projects">
<title>External Projects</title>
<para>
<productname>PostgreSQL</productname> is a large piece of very
complex software, and managing the code is a difficult process. We
have found that many enhancements to
<productname>PostgreSQL</productname> can be more efficiently
developed independently of the main project. They can have their own
developer teams, email lists, their own bug tracking, and their own
release schedule. While their independence makes development easier,
it makes users job harder. They have to hunt around looking for
database enhancements to meet their needs.
</para>
<para>
This section will outlines some of the more popular externally
<productname>PostgreSQL</productname> is a complex software project,
and managing it is difficult. We have found that many
enhancements to <productname>PostgreSQL</productname> can be more
efficiently developed independently of the main project. They can
have their own developer teams, email lists, their own bug tracking,
and their own release schedule. While their independence makes
development easier, it makes user's jobs harder. They have to hunt
around looking for database enhancements to meet their needs.
This section outlines some of the more popular externally
developed enhancements and guides you on how to find them.
</para>
...
...
@@ -30,13 +26,13 @@ $PostgreSQL: pgsql/doc/src/sgml/external-projects.sgml,v 1.3 2004/12/03 06:18:12
</indexterm>
<para>
<productname>PostgreSQL</productname>
packag
es very few interfaces
<productname>PostgreSQL</productname>
includ
es very few interfaces
with the base distribution. <application>libpq</> is packaged because
it is the primary <application>C</> interface and many other
interfaces are built on top of it. <application>ecpg</> is packaged
because it is tied to the server-side grammar so
it
is very dependent
because it is tied to the server-side grammar so is very dependent
on the database version. All the other interfaces are independent
projects.
projects
and must be installed separately
.
</para>
<para>
...
...
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