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
de8113fc
Commit
de8113fc
authored
Nov 22, 2004
by
Tom Lane
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update release notes for recent changes; also minor editorialization.
parent
294c34bb
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
30 additions
and
13 deletions
+30
-13
doc/src/sgml/release.sgml
doc/src/sgml/release.sgml
+30
-13
No files found.
doc/src/sgml/release.sgml
View file @
de8113fc
<!--
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.31
0 2004/11/21 21:17:02
tgl Exp $
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.31
1 2004/11/22 00:37:59
tgl Exp $
-->
<appendix id="release">
...
...
@@ -10,7 +10,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp
<note>
<title>Release date</title>
<simpara>2004-??-??, current as of 2004-11-
06
</simpara>
<simpara>2004-??-??, current as of 2004-11-
21
</simpara>
</note>
<sect2>
...
...
@@ -352,8 +352,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp
<para>
Syntax checking of array input values has been tightened up
considerably. Junk that was previously allowed in odd places with
odd results now causes an
<literal>ERROR. Empty-string element
values must now be written as
""</>, rather than writing nothing.
odd results now causes an
error. Empty-string element values
must now be written as <literal>
""</>, rather than writing nothing.
Also changed behavior with respect to whitespace surrounding
array elements: trailing whitespace is now ignored, for symmetry
with leading whitespace (which has always been ignored).
...
...
@@ -610,7 +610,8 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp
(Manfred Koizar)
</para>
<para>
This gives better statistics for asymmetric data distributions.
This gives better statistics when the density of valid rows is very
different in different regions of a table.
</para>
</listitem>
...
...
@@ -765,12 +766,24 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp
</para>
</listitem>
<listitem>
<para>
Some logging-related configuration parameters could formerly be adjusted
by ordinary users, but only in the <quote>more verbose</> direction.
They are now treated more strictly: only superusers can set them.
However, a superuser may use <command>ALTER USER</> to provide per-user
settings of these values for non-superusers. Also, it is now possible
for superusers to set values of superuser-only configuration parameters
via <literal>PGOPTIONS</>.
</para>
</listitem>
<listitem>
<para>
Allow configuration files to be placed outside the data directory (mlw)
</para>
<para>
By default, configuration files
sit in the top server
directory.
By default, configuration files
are kept in the cluster's top
directory.
With this addition, configuration files can be placed outside the
data directory, easing administration.
</para>
...
...
@@ -1070,7 +1083,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp
columns (Tom)
</para>
<para>
This
is related to the new capability of add
ing defaults for new
This
falls out from the new capability of specify
ing defaults for new
columns.
</para>
</listitem>
...
...
@@ -1141,7 +1154,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp
<listitem>
<para>
Hav
e <command>ALTER TABLE OWNER</> change dependent sequence
Mak
e <command>ALTER TABLE OWNER</> change dependent sequence
ownership too (Alvaro)
</para>
</listitem>
...
...
@@ -1471,7 +1484,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp
<listitem>
<para>
Fix <function>
to_char
(year)</> for BC dates (previously it
Fix <function>
date_part
(year)</> for BC dates (previously it
returned one less than the correct year) (Bruce)
</para>
</listitem>
...
...
@@ -1831,6 +1844,10 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp
Use dependency information to improve the reliability of
<application>pg_dump</> (Tom)
</para>
<para>
This should solve the longstanding problems with related objects
sometimes being dumped in the wrong order.
</para>
</listitem>
<listitem>
...
...
@@ -1937,15 +1954,15 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.310 2004/11/21 21:17:02 tgl Exp
<listitem>
<para>
Many ecpg improvements, including <command>SET DESCRIPTOR</> (Michael)
Add <function>PQprepare/PQsendPrepared()</> functions to support
preparing statements without necessarily specifying the data types
of their parameters (Abhijit Menon-Sen)
</para>
</listitem>
<listitem>
<para>
Add <function>PQprepare/PQsendPrepared()</> functions to support
preparing statements without necessarily specifying the data types
of their parameters (Abhijit Menon-Sen)
Many ecpg improvements, including <command>SET DESCRIPTOR</> (Michael)
</para>
</listitem>
...
...
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