(hope I got 'em all). Per discussion, this release will be 9.0 not 8.5.
#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.63 for PostgreSQL 8.5devel.
+# Generated by GNU Autoconf 2.63 for PostgreSQL 9.0devel.
#
#
# Identity of this package.
PACKAGE_NAME='PostgreSQL'
PACKAGE_TARNAME='postgresql'
-PACKAGE_VERSION='8.5devel'
-PACKAGE_STRING='PostgreSQL 8.5devel'
+PACKAGE_VERSION='9.0devel'
+PACKAGE_STRING='PostgreSQL 9.0devel'
ac_unique_file="src/backend/access/common/heaptuple.c"
# Omit some internal or obsolete options to make the list less imposing.
# This message is too long to be a string in the A/UX 3.1 sh.
cat <<_ACEOF
-\`configure' configures PostgreSQL 8.5devel to adapt to many kinds of systems.
+\`configure' configures PostgreSQL 9.0devel to adapt to many kinds of systems.
Usage: $0 [OPTION]... [VAR=VALUE]...
if test -n "$ac_init_help"; then
case $ac_init_help in
- short | recursive ) echo "Configuration of PostgreSQL 8.5devel:";;
+ short | recursive ) echo "Configuration of PostgreSQL 9.0devel:";;
esac
cat <<\_ACEOF
test -n "$ac_init_help" && exit $ac_status
if $ac_init_version; then
cat <<\_ACEOF
-PostgreSQL configure 8.5devel
+PostgreSQL configure 9.0devel
generated by GNU Autoconf 2.63
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001,
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
-It was created by PostgreSQL $as_me 8.5devel, which was
+It was created by PostgreSQL $as_me 9.0devel, which was
generated by GNU Autoconf 2.63. Invocation command line was
$ $0 $@
# report actual input values of CONFIG_FILES etc. instead of their
# values after options handling.
ac_log="
-This file was extended by PostgreSQL $as_me 8.5devel, which was
+This file was extended by PostgreSQL $as_me 9.0devel, which was
generated by GNU Autoconf 2.63. Invocation command line was
CONFIG_FILES = $CONFIG_FILES
_ACEOF
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
ac_cs_version="\\
-PostgreSQL config.status 8.5devel
+PostgreSQL config.status 9.0devel
configured by $0, generated by GNU Autoconf 2.63,
with options \\"`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`\\"
dnl Process this file with autoconf to produce a configure script.
-dnl $PostgreSQL: pgsql/configure.in,v 1.622 2010/02/13 02:34:11 tgl Exp $
+dnl $PostgreSQL: pgsql/configure.in,v 1.623 2010/02/17 04:19:37 tgl Exp $
dnl
dnl Developers, please strive to achieve this order:
dnl
dnl
m4_pattern_forbid(^PGAC_)dnl to catch undefined macros
m4_if(m4_defn([m4_PACKAGE_VERSION]), [2.63], [], [m4_fatal([Autoconf version 2.63 is required.
Untested combinations of 'autoconf' and PostgreSQL versions are not
*
*
* IDENTIFICATION
- * $PostgreSQL: pgsql/contrib/vacuumlo/vacuumlo.c,v 1.44 2010/01/02 16:57:33 momjian Exp $
+ * $PostgreSQL: pgsql/contrib/vacuumlo/vacuumlo.c,v 1.45 2010/02/17 04:19:37 tgl Exp $
*
*-------------------------------------------------------------------------
*/
*/
buf[0] = '\0';
strcat(buf, "CREATE TEMP TABLE vacuum_l AS ");
- if (PQserverVersion(conn) >= 80500)
+ if (PQserverVersion(conn) >= 90000)
strcat(buf, "SELECT oid AS lo FROM pg_largeobject_metadata");
else
strcat(buf, "SELECT DISTINCT loid AS lo FROM pg_largeobject");
Operating System (example: Linux 2.4.18) :
- PostgreSQL version (example: PostgreSQL 8.5devel): PostgreSQL 8.5devel
+ PostgreSQL version (example: PostgreSQL 9.0devel): PostgreSQL 9.0devel
Compiler used (example: gcc 3.3.5) :
-
+
- Prior to
PostgreSQL> 8.5, there was no permission structure
+ Prior to
PostgreSQL> 9.0, there was no permission structure
associated with large objects. As a result,
pg_largeobject was publicly readable and could be
used to obtain the OIDs (and contents) of all large objects in the system.
-
+
Server Configuration
- In
PostgreSQL> releases prior to 8.5, large objects
+ In
PostgreSQL> releases prior to 9.0, large objects
did not have access privileges and were, in effect, readable and
writable by all users. Setting this variable to on>
disables the new privilege checks, for compatibility with prior
Setting this variable does not disable all security checks for
- large objects - only those for which the default behavior has changed
+ large objects — only those for which the default behavior has
+
changed in PostgreSQL> 9.0.
For example, lo_import() and
lo_export() need superuser privileges independent
of this setting.
-
+
Data Types
of these are always accepted on input. The output format depends
on the configuration parameter ;
the default is hex. (Note that the hex format was introduced in
-
PostgreSQL 8.5; earlier versions and some
+
PostgreSQL 9.0; earlier versions and some
tools don't understand it.)
-
+
- Before PostgreSQL 8.5, the SQL keyword was optional,
+ Before PostgreSQL 9.0, the SQL keyword was optional,
so using DESCRIPTOR and SQL DESCRIPTOR
produced named SQL Descriptor Areas. Now it is mandatory, omitting
the SQL keyword produces SQLDA Descriptor Areas,
-
+
-8.5 SYSTEM "release-8.5.sgml">
+9.0 SYSTEM "release-9.0.sgml">
-
+
High Availability, Load Balancing, and Replication
- Starting with
PostgreSQL> version 8.5, you can use
+ Starting with
PostgreSQL> version 9.0, you can use
streaming replication (see ) to
achieve the same with less effort.
-
+
hstore
- As of PostgreSQL 8.5, hstore> uses a different internal
+ As of PostgreSQL 9.0, hstore> uses a different internal
representation than previous versions. This presents no obstacle for
dump/restore upgrades since the text representation (used in the dump) is
unchanged.
-
+
standard_conforming_strings> was not reported by releases
before 8.1;
IntervalStyle> was not reported by releases before 8.4;
- application_name> was not reported by releases before 8.5.)
+ application_name> was not reported by releases before 9.0.)
Note that
server_version>,
server_encoding> and
-
+
Large Objects
- As of
PostgreSQL> 8.5, large objects have an owner
+ As of
PostgreSQL> 9.0, large objects have an owner
and a set of access permissions, which can be managed using
and
.
-
+
PL/pgSQL - SQL Procedural Language
- In
PostgreSQL> 8.5 and later,
+ In
PostgreSQL> 9.0 and later,
PL/pgSQL is installed by default.
However it is still a loadable module, so especially security-conscious
administrators could choose to remove it.
-
PostgreSQL versions before
8.5 would try
+
PostgreSQL versions before
9.0 would try
to substitute the variable in all three cases, leading to syntax errors.
large body of
PL/pgSQL> code. In such cases you can
specify that
PL/pgSQL> should resolve ambiguous references
as the variable (which is compatible with
PL/pgSQL>'s
- behavior before
PostgreSQL 8.5), or as the
+ behavior before
PostgreSQL 9.0), or as the
table column (which is compatible with some other systems such as
-
+
Frontend/Backend Protocol
standard_conforming_strings> was not reported by releases
before 8.1;
IntervalStyle> was not reported by releases before 8.4;
- application_name> was not reported by releases before 8.5.)
+ application_name> was not reported by releases before 9.0.)
Note that
server_version>,
server_encoding> and
The following syntax was used before
PostgreSQL>
- version 8.5 and is still supported:
+ version 9.0 and is still supported:
COPY table_name [ ( column [, ...] ) ]
Only the ANALYZE and VERBOSE options
can be specified, and only in that order, without surrounding the option
- list in parentheses. Prior to
PostgreSQL 8.5,
+ list in parentheses. Prior to
PostgreSQL 9.0,
the unparenthesized syntax was the only one supported. It is expected that
all new options will be supported only in the parenthesized syntax.
When the option list is surrounded by parentheses, the options can be
written in any order. Without parentheses, options must be specified
in exactly the order shown above.
- Prior to
PostgreSQL 8.5, the unparenthesized
+ Prior to
PostgreSQL 9.0, the unparenthesized
syntax was the only one supported. It is expected that all new options
will be supported only in the parenthesized syntax.
-
+
-8-5">
-
Release 8.5alpha3
+9-0">
+
Release 9.0alpha3
Overview
-
+
-&release-8.5;
+&release-9.0;
&release-8.4;
&release-8.3;
&release-8.2;