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
ebfa6ab7
Commit
ebfa6ab7
authored
26 years ago
by
Bruce Momjian
Browse files
Options
Downloads
Patches
Plain Diff
Update sgml for 6.4.* release changes.
parent
bfcf9060
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/src/sgml/release.sgml
+112
-0
112 additions, 0 deletions
doc/src/sgml/release.sgml
with
112 additions
and
0 deletions
doc/src/sgml/release.sgml
+
112
−
0
View file @
ebfa6ab7
<Chapter Id="release">
<Chapter Id="release">
<Title>Release Notes</Title>
<Title>Release Notes</Title>
<Sect1>
<Title>Release 6.4.2</Title>
<!--
<docinfo>
<authorgroup>
<author>
<firstname>Bruce</firstname>
<surname>Momjian</surname>
</author>
</authorgroup>
<date>1999-12-20</date>
</docinfo>
-->
<para>
The 6.4.1 release was improperly packaged. This also has one additional
bug fix.
</para>
<sect2>
<title>Migration to v6.4.2</title>
<para>
A dump/restore is <emphasis>not</emphasis> required for those running
6.4.*.
</para>
</sect2>
<sect2>
<title>Detailed Change List</title>
<para>
<programlisting>
Fix for datetime constant problem on some platforms(Thomas)
</programlisting>
</Para>
</sect2>
</Sect1>
<Sect1>
<Title>Release 6.4.1</Title>
<!--
<docinfo>
<authorgroup>
<author>
<firstname>Bruce</firstname>
<surname>Momjian</surname>
</author>
</authorgroup>
<date>1999-12-18</date>
</docinfo>
-->
<para>
This is basically a cleanup release for 6.4. We have fixed a variety of
problems reported by 6.4 users.
</para>
<sect2>
<title>Migration to v6.4</title>
<para>
A dump/restore is <emphasis>not</emphasis> required for those running
6.4.
</para>
</sect2>
<sect2>
<title>Detailed Change List</title>
<para>
<programlisting>
Add pg_dump -N flag to force double quotes around identifiers. This is
the default(Thomas)
Fix for NOT in where clause causing crash(Bruce)
EXPLAIN VERBOSE coredump fix(Vadim)
Fix shared-library problems on Linux
Fix test for table existance to allow mixed-case and whitespace in
the table name(Thomas)
Fix a couple of pg_dump bugs
Configure matches template/.similar entries better(Tom)
Change builtin function names from SPI_* to spi_*
OR WHERE clause fix(Vadim)
Fixes for mixed-case table names(Billy)
contrib/linux/postgres.init.csh/sh fix(Thomas)
libpq memory overrun fix
SunOS fixes(Tom)
Change exp() behavior to generate error on underflow(Thomas)
pg_dump fixes for memory leak, inheritance constraints, layout change
update pgaccess to 0.93
Fix prototype for 64-bit platforms
Multi-byte fixes(Tatsuo)
New ecpg man page
Fix memory overruns(Tatsuo)
Fix for lo_import() crash(Bruce)
Better search for install program(Tom)
Timezone fixes(Tom)
HPUX fixes(Tom)
Use implicit type coersion for matching DEFAULT values(Thomas)
Add routines to help with single-byte (internal) character type(Thomas)
Compilation of libpq for Win32 fixes(Magnus)
Upgrade to PyGreSQL 2.2(D'Arcy)
</programlisting>
</Para>
</sect2>
</Sect1>
<Sect1>
<Sect1>
<Title>Release 6.4</Title>
<Title>Release 6.4</Title>
<!--
<!--
...
...
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