| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
Mostly bug fixes. The full list of changes can be found at:
7.3.5: http://www.postgresql.org/news/164.html
7.3.6: http://www.postgresql.org/news/172.html
As with all minor release upgrades a dump/restore is not required.
|
|
Remove files and patches in the py-postgresql directory and add necessary
ones in the postgresql directory.
|
|
==================================================================
| NOTE: A dump-and-restore is required to update your databases |
| if you wish to update postgresql-server. If your |
| application examines the system catalogs, additional |
| changes will be required due to the introduction of |
| schemas in 7.3; for more information, see: |
| |
| http://www.ca.postgresql.org/docs/momjian/upgrade_tips_7.3 |
==================================================================
Major changes from version 7.2.3 include:
Schemas
Schemas allow users to create objects in separate namespaces,
so two people or applications can have tables with the same
name. There is also a public schema for shared tables.
Table/index creation can be restricted by removing permissions
on the public schema.
Drop Column
PostgreSQL now supports the ALTER TABLE ... DROP COLUMN
functionality.
Table Functions
Functions returning multiple rows and/or multiple columns are
now much easier to use than before. You can call such a "table
function" in the SELECT FROM clause, treating its output like a
table. Also, PL/pgSQL functions can now return sets.
Prepared Queries
PostgreSQL now supports prepared queries, for improved
performance.
Dependency Tracking
PostgreSQL now records object dependencies, which allows
improvements in many areas. "DROP" statements now take either
CASCADE or RESTRICT to control whether dependent objects are
also dropped.
Privileges
Functions and procedural languages now have privileges, and
functions can be defined to run with the privileges of their
creator.
Internationalization
Both multibyte and locale support are now always enabled.
Logging
A variety of logging options have been enhanced.
Interfaces
A large number of interfaces have been moved to
http://gborg.postgresql.org where they can be developed and
released independently.
Functions/Identifiers
By default, functions can now take up to 32 parameters, and
identifiers can be up to 63 bytes long. Also, OPAQUE is now
deprecated: there are specific "pseudo-datatypes" to represent
each of the former meanings of OPAQUE in function argument and
result types.
|
|
*** Please note that a dump/restore is NOT required for those ***
*** running PostgreSQL 7.2. ***
Important changes from version 7.2 include:
Ensure that sequence counters do not go backwards after a crash (Tom)
Allow psql \connect to handle mixed case database and user names (Tom)
Return proper OID on command completion even with ON INSERT rules (Tom)
Allow COPY FROM to use 8-bit DELIMITERS (Tatsuo)
Improve handling of multiple UNIONs with different lengths (Tom)
Fix for array subscripts handling (Tom)
Allow EXECUTE of "CREATE TABLE AS ... SELECT" in PL/PgSQL (Tom)
|
|
<explorer@flame.org> for most of the work on this update.
Pkgsrc changes from the previous version include removing Makefile.ssl and
some patches that have been integrated into this release of PostgreSQL. We
leave open the question of when to byte-compile the Python modules for the
PyGreSQL interface and just do it as before, although we should consider
doing the compilation as a post-install step to ensure that the timestamps
are correct. We also reorder some lines in the Makefile to include
Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY)
as they may possibly trigger different portions of Makefile.common.
*** Please note that a dump/restore is required to migrate an existing ***
*** PostgreSQL installation to 7.2. ***
Major changes from version 7.1.3 are geared toward improving use in
high-volume applications and include:
VACUUM
Vacuuming no longer locks tables, thus allowing normal user access
during the vacuum. A new "VACUUM FULL" command does old-style
vacuum by locking the table and shrinking the on-disk copy of the
table.
Transactions
There is no longer a problem with installations that exceed four
billion transactions.
OID's
OID's are now optional. Users can now create tables without OID's
for cases where OID usage is excessive.
Optimizer
The system now computes histogram column statistics during
"ANALYZE", allowing much better optimizer choices.
Security
A new MD5 encryption option allows more secure storage and
transfer of passwords. A new Unix-domain socket authentication
option is available on Linux and BSD systems. PAM authentication
is also available.
Statistics
Administrators can use the new table access statistics module to
get fine-grained information about table and index usage.
|
|
found at run-time, as before, the -Wl,-R options that set the run-time
library search path weren't being used. Simply using LDFLAGS without
filtering doesn't work because the configure script appends CFLAGS to
LDFLAGS, and some commonly-used compiler options, e.g. -mcpu=..., which
causes python's makesetup to choke because the options aren't in the list
of recognized linker options. Thanks to D'Arcy J.M. Cain <darcy@druid.net>
for pointing out the error and possible solution.
|
|
next distribution. This patch brings it up to date now. Major fixes:
- Support for more types. This fixes a bug introduced in the current
PostgreSQL because of the different way of handling agregates.
- Add WIN32 support
- Fix some DB-API quoting problems
|
|
Relevant changes from version 7.1.2 include:
Remove unused WAL segements of large transactions
Multiaction rule fix
Pl/pgSQL memory allocation fix
VACUUM buffer fix
pg_dump fixes for GRANT/REVOKE/comments on views, user-defined types
Fix subselects with DISTINCT ON or LIMIT
Disable COPY TO/FROM a view
|
|
preinstalled libssl and libcrypto.
|
|
problems early on if insufficient libraries are specified during linking.
Move the configure script patch to the last patch of the group so that
the configure script will have the most recent timestamp.
|
|
postgresql-lib
postgresql-client
postgresql-server
postgresql-doc
with postgresql as a meta-package. Major changes from version 7.1.1
include:
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 - 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
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.
Migration to 7.1.1
A dump/restore using pg_dump is required for those wishing to migrate
data from any previous release.
|
|
|
|
|
|
|
|
* Enhance rc.d/pgsql.sh script to accept start/stop/restart.
* Add fixes for alpha from Kevin P. Neal <kpn@neutralgood.org> in PR#10543.
XXX Includes a patch which removes inlining of the alpha's TAS function.
XXX This is apparently some code-gen bug in GCC for alpha.
* Fix many CLUSTER failures (Tom)
* Allow ALTER TABLE RENAME works on indexes (Tom)
* Fix plpgsql to handle datetime->timestamp and timespan->interval (Bruce)
* New configure --with-setproctitle switch to use setproctitle() (Marc, Bruce)
* Fix the off by one errors in ResultSet from 6.5.3, and more.
* jdbc ResultSet fixes (Joseph Shraibman)
* optimizer tunings (Tom)
* Fix create user for pgaccess
* Fix for UNLISTEN failure
* Reduce COPY IN lock level (Tom)
* Change libpqeasy to use PQconnectdb() style parameters (Bruce)
* Fix pg_dump to handle OID indexes (Tom)
* Fix small memory leak (Tom)
* Solaris fix for createdb/dropdb (Tatsuo)
* Fix for non-blocking connections (Alfred Perlstein)
* Fix improper recovery after RENAME TABLE failures (Tom)
* Copy pg_ident.conf.sample into /lib directory in install (Bruce)
* Add SJIS UDC (NEC selection IBM kanji) support (Eiji Tokuya)
* Fix too long syslog message (Tatsuo)
* Fix problem with quoted indexes that are too long (Tom)
* JDBC ResultSet.getTimestamp() fix (Gregory Krasnow & Floyd Marinescu)
* ecpg changes (Michael)
|
|
|
|
|
|
A HUGE number of bug/performance fixes and minor enhancements.
Foreign Keys
Foreign keys are now implemented, with the exception of PARTIAL
MATCH foreign keys. Many users have been asking for this
feature, and we are pleased to offer it.
Optimizer Overhaul
Continuing on work started a year ago, the optimizer has been
overhauled, allowing improved query execution and better
performance with less memory usage.
Updated psql
psql, our interactive terminal monitor, has been updated with a
variety of new features. See the psql manual page for details.
Upcoming Features
In 7.1 or 7.2, we plan to have outer joins, storage for very
long rows, and a write-ahead logging system.
A dump/restore using pg_dump is required for those wishing to migrate
data from any previous release. For those upgrading from 6.5.*, you
can use pg_upgrade to upgrade to this release.
|
|
|
|
unlibtoolized. Things now install into ${PREFIX} instead of
${PREFIX}/${PGSQL_USER} to match hier(7) expectations. The Tcl and Tk
interfaces are now split out into separate packages.
This closes the following PRs: 7384, 8747, 8789, 9272, 9461.
|
|
(i.e. ELF on former a.out ports) are namespace-clean wrt. this, and the latter
predefine implies the former.
|
|
out of synch)
|
|
doesn't use it. Later tonight or tomorrow morning, I will commit a jdbc-postgresql
package which will share DISTFILE and patch goo with this package.
All this may eventually be replaced if the client stuff is factored out of the
postgresql package, but that's not me.
|
|
from the main PostgreSQL distribution, and must be installed separately
(databases/pgaccess). Relevant changes from 6.5.1:
subselect+CASE fixes(Tom)
Add SHLIB_LINK setting for solaris_i386 and solaris_sparc ports(Daren
Sefcik)
Fixes for CASE in WHERE join clauses(Tom)
Fix BTScan abort(Tom)
Repair the check for redundant UNIQUE and PRIMARY KEY indices(Thomas)
Improve it so that it checks for multi-column constraints(Tom)
Fix for Win32 making problem with MB enabled(Hiroki Kataoka)
Allow BSD yacc and bison to compile pl code(Bruce)
Fix SET NAMES
int8 fixes(Thomas)
Fix vacuum's memory consumption(Hiroshi,Tatsuo)
Reduce the total memory consumption of vacuum(Tom)
Fix for timestamp(datetime)
Rule deparsing bugfixes(Tom)
Fix quoting problems in mkMakefile.tcldefs.sh.in and
mkMakefile.tkdefs.sh.in(Tom)
This is to re-use space on index pages freed by vacuum(Vadim)
document -x for pg_dump(Bruce)
Fix for unary operators in rule deparser(Tom)
Comment out FileUnlink of excess segments during mdtruncate()(Tom)
Irix linking fix from Yu Cao <yucao@falcon.kla-tencor.com>
Repair logic error in LIKE: should not return LIKE_ABORT
when reach end of pattern before end of text(Tom)
Repair incorrect cleanup of heap memory allocation during transaction
abort(Tom)
|
|
removed, but this should still function correctly on a.out systems. This
package was originally submitted by D'Arcy J.M. Cain, but with major
overhauling by me.
Closes PR#7865 and relevant part of PR#8299.
Major changes from version 6.4.2:
Multi-version concurrency control(MVCC)
This removes our old table-level locking, and replaces it with a
locking system that is superior to most commercial database
systems. In a traditional system, each row that is modified is
locked until committed, preventing reads by other users. MVCC
uses the natural multi-version nature of PostgreSQL to allow
readers to continue reading consistent data during writer
activity. Writers continue to use the compact pg_log transaction
system. This is all performed without having to allocate a lock
for every row like traditional database systems. So, basically,
we no longer are restricted by simple table-level locking; we
have something better than row-level locking.
Hot backups from pg_dump
pg_dump takes advantage of the new MVCC features to give a
consistant database dump/backup while the database stays online
and available for queries.
Numeric data type
We now have a true numeric data type, with user-specified
precision.
Temporary tables
Temporary tables are guaranteed to have unique names within a
database session, and are destroyed on session exit.
New SQL features
We now have CASE, INTERSECT, and EXCEPT statement support. We
have new LIMIT/OFFSET, SET TRANSACTION ISOLATION LEVEL, SELECT
... FOR UPDATE, and an improved LOCK TABLE command.
Speedups
We continue to speed up PostgreSQL, thanks to the variety of
talents within our team. We have sped up memory allocation,
optimization, table joins, and row transfer routines.
Ports
We continue to expand our port list, this time including
WinNT/ix86 and NetBSD/arm32.
Interfaces
Most interfaces have new versions, and existing functionality
has been improved.
Documentation
New and updated material is present throughout the
documentation. New FAQs have been contributed for SGI and AIX
platforms. The Tutorial has introductory information on SQL from
Stefan Simkovics. For the User's Guide, there are reference pages
covering the postmaster and more utility programs, and a new
appendix contains details on date/time behavior. The
Administrator's Guide has a new chapter on troubleshooting from
Tom Lane. And the Programmer's Guide has a description of query
processing, also from Stefan, and details on obtaining the
Postgres source tree via anonymous CVS and CVSup.
|
|
Add NetBSD Id to patch-ae.
s|/usr/sbin/chown|${CHOWN}|
s|/bin/chmod|${CHMOD}|
|
|
Fixes PR pkg/7959.
|
|
From Andrew McMurry <a.mcmurry1@physics.oxford.ac.uk>.
|
|
|
|
|
|
- add INSTALL_TARGET=install install-man and remove the patch that did
modify the GNUMakefile, for better maintainance.
- add - in front of @${MKDIR} to silently fail if the dir already exists
- move ld.so.conf warning near the end, so it can be better spotted.
|
|
adds patches for m68k support, provided in pr 6664 by MOCHIDA Shuji.
|
|
|
|
They told me to say that.
Use addnerd to create the user.
|
|
Add pgaccess to the list of programs to 'do' when USE_TCL is defined.
Add a Makefile for pgaccess, so that it gets installed with the right
embedded interpreter.
|
|
relative to ${PREFIX}.
|
|
|
|
${PREFIX}/include, and libraries in ${PREFIX}/lib, rather than having
them hardcoded.
|
|
Management System, into the NetBSD packages collection, from the
FreeBSD port.
|
