| Age | Commit message (Collapse) | Author |
|---|
|
launcher daemon.
|
|
"autovacuum = off", the system may still periodically start autovacuum
processes to prevent XID wraparound. Patch from David Fetter, with
editorializing.
|
|
* Add support for SQL-standard GENERATED/IDENTITY columns
> http://archives.postgresql.org/pgsql-hackers/2007-05/msg00344.php
> http://archives.postgresql.org/pgsql-patches/2007-05/msg00076.php
|
|
|
|
< o Add support for arrays of complex types
>
> http://archives.postgresql.org/pgsql-patches/2007-05/msg00114.php
>
> o -Add support for arrays of complex types
|
|
> * Have configure choose integer datetimes by default
>
> http://archives.postgresql.org/pgsql-patches/2007-05/msg00046.php
|
|
> o Allow data to be passed in native language formats, rather
> than only text
> http://archives.postgresql.org/pgsql-hackers/2007-05/msg00289.php
|
|
named foo, would work but the other ordering would not. If a user-specified
type or table name collides with an existing auto-generated array name, just
rename the array type out of the way by prepending more underscores. This
should not create any backward-compatibility issues, since the cases in which
this will happen would have failed outright in prior releases.
Also fix an oversight in the arrays-of-composites patch: ALTER TABLE RENAME
renamed the table's rowtype but not its array type.
|
|
needs to check the new constraint against columns of derived domains too.
Also, make it error out if the domain to be modified is used within any
composite-type columns. Eventually we should support that case, but it seems
a bit painful, and not suitable for a back-patch. For the moment just let the
user know we can't do it.
Backpatch to 8.2, which is the only released version that allows nested
domains. Possibly the other part should be back-patched further.
|
|
|
|
and views (but not system catalogs, nor sequences or toast tables). Get rid
of the hardwired convention that a type's array type is named exactly "_type",
instead using a new column pg_type.typarray to provide the linkage. (It still
will be named "_type", though, except in odd corner cases such as
maximum-length type names.)
Along the way, make tracking of owner and schema dependencies for types more
uniform: a type directly created by the user has these dependencies, while a
table rowtype or auto-generated array type does not have them, but depends on
its parent object instead.
David Fetter, Andrew Dunstan, Tom Lane
|
|
sign convention from everyplace else in Postgres. I don't suppose that
this will stop people from being confused, but at least we can say that
it's documented.
|
|
|
|
|
|
< Last updated: Sat May 5 10:47:39 EDT 2007
> Last updated: Sat May 5 11:39:57 EDT 2007
< * Flush cached query plans when the dependent objects change,
< when the cardinality of parameters changes dramatically, or
> * -Flush cached query plans when the dependent objects change or
<
< A more complex solution would be to save multiple plans for different
< cardinality and use the appropriate plan based on the EXECUTE values.
<
< * Track dependencies in function bodies and recompile/invalidate
<
< This is particularly important for references to temporary tables
< in PL/PgSQL because PL/PgSQL caches query plans. The only workaround
< in PL/PgSQL is to use EXECUTE. One complexity is that a function
< might itself drop and recreate dependent tables, causing it to
< invalidate its own query plan.
<
< * Invalidate prepared queries, like INSERT, when the table definition
> * -Track dependencies in function bodies and recompile/invalidate
> * -Invalidate prepared queries, like INSERT, when the table definition
|
|
< * Invalidate prepared queries, like INSERT, when the table definition
< is altered
>
> * Invalidate prepared queries, like INSERT, when the table definition
> is altered
|
|
> o -Allow multiple vacuums so large tables do not starve small
|
|
|
|
|
|
|
|
|
|
> * -Allow ORDER BY ... LIMIT # to select high/low value without sort or
<
< Right now, if no index exists, ORDER BY ... LIMIT # requires we sort
< all values to return the high/low value. Instead The idea is to do a
< sequential scan to find the high/low value, thus avoiding the sort.
< MIN/MAX already does this, but not for LIMIT > 1.
<
|
|
to clarify the situation that Theo Schlossnagle recently reported on -bugs.
|
|
|
|
the relevant fixes to 8.2 as well.
|
|
< * Make standard_conforming_strings the default in 8.3?
> * Make standard_conforming_strings the default in 8.4?
|
|
< o Add support for MOVE and SCROLL cursors
<
< PL/pgSQL cursors should support the same syntax as
< backend cursors.
<
> o -Add support for MOVE cursors
> o Add support for SCROLL cursors
|
|
by Pavel Stehule, and reviewed by Neil Conway.
|
|
for consistency with the backend's FETCH command. Patch from Pavel
Stehule, reviewed by Neil Conway.
|
|
now enables row-level stats, the out of the box stats volume is no
longer particularly low.
|
|
table entries describing functions with periods.
|
|
|
|
RESET SESSION, RESET PLANS, and RESET TEMP are now DISCARD ALL,
DISCARD PLANS, and DISCARD TEMP, respectively. This is to avoid
confusion with the pre-existing RESET variants: the DISCARD
commands are not actually similar to RESET. Patch from Marko
Kreen, with some minor editorialization.
|
|
|
|
|
|
Jun Kuwamura
|
|
|
|
<H3 id="item3.6">3.6) What is the upgrade process for
PostgreSQL?</H3>
to reference both versioning and specific upgrade instructions.
|
|
|
|
> o -Allow commenting of variables in postgresql.conf to restore them
|
|
library. New configure option --with-ossp-uuid to activate.
|
|
|
|
|
|
|
|
Security: CVE-2007-2138
|
|
This is needed to allow a security-definer function to set a truly secure
value of search_path. Without it, a malicious user can use temporary objects
to execute code with the privileges of the security-definer function. Even
pushing the temp schema to the back of the search path is not quite good
enough, because a function or operator at the back of the path might still
capture control from one nearer the front due to having a more exact datatype
match. Hence, disable searching the temp schema altogether for functions and
operators.
Security: CVE-2007-2138
|
|
|
|
|
|
|
|
|
