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
5dc0e67b
Commit
5dc0e67b
authored
24 years ago
by
Peter Eisentraut
Browse files
Options
Downloads
Patches
Plain Diff
Reformat the "major changes" to 72 or so columns.
parent
11fd9157
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
HISTORY
+19
-17
19 additions, 17 deletions
HISTORY
with
19 additions
and
17 deletions
HISTORY
+
19
−
17
View file @
5dc0e67b
...
...
@@ -11,32 +11,34 @@ PostgreSQL code for many years.
Major changes in this release:
Write-ahead Log (WAL) - To maintain database consistency in case
of an operating system crash, previous releases of PostgreSQL have
forced all data modifications to disk before each transaction commit.
With WAL, only one log file must be flushed to disk, greatly improving
performance. If you have been using -F in previous releases to disable
disk flushes, you may want to consider discontinuing its use.
Write-ahead Log (WAL) - To maintain database consistency in
case of an operating system crash, previous releases of PostgreSQL
have forced all data modifications to disk before each transaction
commit. With WAL, only one log file must be flushed to disk, greatly
improving performance. If you have been using -F in previous releases
to disable disk flushes, you may want to consider discontinuing its
use.
TOAST - Previous releases had a compiled-in row length limit,
typically 8
k
- 32
k.
This limit made storage of long text fields
difficult. With TOAST, long rows of any length can be stored with
good
performance.
typically 8 - 32
kB.
This limit made storage of long text fields
difficult. With TOAST, long rows of any length can be stored with
good
performance.
Outer Joins - We now support outer joins. The UNION/NOT IN
workaround for outer joins is no longer required. We use the SQL92
outer join syntax.
Function Manager - The previous C function manager did not handle NULLs properly,
nor did it support 64-bit CPU's (Alpha). The new function manager does. You can continue
using your old custom functions, but you may want to rewrite them in the future to use the
Function Manager - The previous C function manager did not
handle NULLs properly, nor did it support 64-bit CPU's (Alpha). The
new function manager does. You can continue using your old custom
functions, but you may want to rewrite them in the future to use the
new function manager call interface.
Complex Queries - A large number of complex queries that were
unsupported in previous releases now work. Many combinations of
views,
aggregates, UNION, LIMIT, cursors, subqueries, and inherited
tables
now work properly. Inherited tables are now accessed by
default.
Subqueries in FROM are now supported.
unsupported in previous releases now work. Many combinations of
views,
aggregates, UNION, LIMIT, cursors, subqueries, and inherited
tables
now work properly. Inherited tables are now accessed by
default.
Subqueries in FROM are now supported.
Migration to 7.1
...
...
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