| Commit message (Collapse) | Author | Age |
|
|
|
| |
> * Bruce is Bruce Momjian <bruce@momjian.us> of EnterpriseDB
|
|
|
|
|
|
| |
< * Reuse index tuples that point to rows that are not visible to anyone?
> * Reuse index tuples that point to heap tuples that are not visible to
> anyone?
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
< * Allow heap reuse of UPDATEd rows if old and new versions are on the
< same heap page?
> * Allow heap reuse of UPDATEd rows if no indexed columns are changed,
> and old and new versions are on the same heap page?
< This is possible for same-page updates because a single index row
< can point to both old and new values.
> While vacuum handles DELETEs fine, updating of non-indexed columns, like
> counters, are difficult for VACUUM to handle efficiently. This method
> is possible for same-page updates because a single index row can be
> used to point to both old and new values.
|
|
|
|
|
|
|
|
|
|
| |
>
> * Allow heap reuse of UPDATEd rows if old and new versions are on the
> same heap page?
>
> This is possible for same-page updates because a single index row
> can point to both old and new values.
> http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php
|
|
|
|
| |
functions.
|
|
|
|
|
|
|
| |
current commands; instead, store current-status information in shared
memory. This substantially reduces the overhead of stats_command_string
and also ensures that pg_stat_activity is fully up to date at all times.
Per my recent proposal.
|
| |
|
|
|
|
|
| |
symlink is kept for now for compatibility. To call single-user mode, use
postgres --single.
|
|
|
|
| |
SQLSTATEs, fix some documentation problems.
|
|
|
|
|
| |
leading zeroes from the SQLSTATE codes. They're strings, people,
not numbers.
|
|
|
|
| |
language, tablespace, trigger, rule, opclass, function, aggregate. operator, and cast.
|
|
|
|
|
|
|
| |
> o Allow PL/python to composite types and result sets
> once buggy assert-enabled versions of python can be detected
>
> http://archives.postgresql.org/pgsql-patches/2006-04/msg00087.php
|
|
|
|
|
|
|
| |
>
> * Fix CREATE CAST on DOMAINs
>
> http://archives.postgresql.org/pgsql-hackers/2006-05/msg00072.php
|
|
|
|
| |
Backpatch documentation addition to 8.1.X.
|
|
|
|
| |
> http://archives.postgresql.org/pgsql-bugs/2006-04/msg00248.php
|
|
|
|
| |
> http://archives.postgresql.org/pgsql-general/2005-08/msg01432.php
|
|
|
|
| |
> http://archives.postgresql.org/pgsql-hackers/2006-03/msg00586.php
|
|
|
|
|
| |
> * Consider shrinking expired tuples to just their headers
> http://archives.postgresql.org/pgsql-patches/2006-03/msg00142.php
|
|
|
|
|
| |
* Auto-fill the free space map by scanning the buffer cache or by
checking pages written by the background writer
|
|
|
|
|
|
| |
>
> http://archives.postgresql.org/pgsql-hackers/2006-02/msg01125.php
>
|
|
|
|
|
|
| |
> * Add support for public SYNONYMS
>
> http://archives.postgresql.org/pgsql-hackers/2006-03/msg00519.php
|
|
|
|
|
| |
>
> http://archives.postgresql.org/pgsql-patches/2006-02/msg00288.php
|
|
|
|
|
|
|
| |
> o Fix problems with RETURN NEXT on tables with
> dropped/added columns after function creation
>
> http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php
|
|
|
|
|
|
| |
> * Allow protocol-level BIND parameter values to be logged
>
> http://archives.postgresql.org/pgsql-hackers/2006-02/msg00165.php
|
|
|
|
|
|
| |
>
> http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php
>
|
|
|
|
| |
Magnus Hagander
|
| |
|
|
|
|
|
| |
< get_employee_salary(emp_id AS 12345, tax_year AS 2001)
> get_employee_salary(12345 AS emp_id, 2001 AS tax_year)
|
| |
|
|
|
|
|
|
|
|
|
| |
less than one row is returned by the SELECT, for Oracle PL/SQL
compatibility.
Improve SELECT INTO documentation.
Matt Miller
|
| |
|
|
|
|
| |
non-PostgreSQL libraries cannot be loaded using this capability.
|
|
|
|
|
| |
< get_employee_salary(emp_id => 12345, tax_year => 2001)
> get_employee_salary(emp_id AS 12345, tax_year AS 2001)
|
|
|
|
|
|
| |
description.
Nis Jorgensen
|
|
|
|
|
|
|
| |
>
> o Fix memory leak from exceptions
>
> http://archives.postgresql.org/pgsql-performance/2006-06/msg00305.php
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
section into PL/pgSQL and non-PL/pgSQL sections:
< o Fix PL/pgSQL RENAME to work on variables other than OLD/NEW
< o Allow function parameters to be passed by name,
< get_employee_salary(emp_id => 12345, tax_year => 2001)
< o Add Oracle-style packages
< o Add table function support to pltcl, plpython
< o Add capability to create and call PROCEDURES
< o Allow PL/pgSQL to handle %TYPE arrays, e.g. tab.col%TYPE[]
< o Allow function argument names to be statements from PL/PgSQL
< o Add MOVE to PL/pgSQL
< o Add support for polymorphic arguments and return types to
< languages other than PL/PgSQL
< o Add support for OUT and INOUT parameters to languages other
< than PL/PgSQL
< o Add single-step debugging of PL/PgSQL functions
< o Allow PL/PgSQL to support WITH HOLD cursors
< o Allow PL/PgSQL RETURN to return row or record functions
<
< http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php
> o PL/pgSQL
> o Fix RENAME to work on variables other than OLD/NEW
> o Allow function parameters to be passed by name,
> get_employee_salary(emp_id => 12345, tax_year => 2001)
> o Add Oracle-style packages
> o Allow handling of %TYPE arrays, e.g. tab.col%TYPE[]
> o Allow listing of record column names, and access to
> record columns via variables, e.g. columns := r.(*),
> tval2 := r.(colname)
>
> http://archives.postgresql.org/pgsql-patches/2005-07/msg00458.php
> http://archives.postgresql.org/pgsql-patches/2006-05/msg00302.php
> http://archives.postgresql.org/pgsql-patches/2006-06/msg00031.php
>
> o Add MOVE
> o Add single-step debugging of functions
> o Add support for WITH HOLD cursors
> o Allow PL/RETURN to return row or record functions
>
> http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php
>
>
> o Other
> o Add table function support to pltcl, plpython
> o Add support for polymorphic arguments and return types to
> languages other than PL/PgSQL
> o Add capability to create and call PROCEDURES
> o Add support for OUT and INOUT parameters to languages other
> than PL/PgSQL
|
|
|
|
|
|
| |
> o Allow PL/PgSQL RETURN to return row or record functions
>
> http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php
|
|
|
|
|
|
|
|
| |
<
< * Consider padding the spinlock structure to have spinlock registers
< on different CPU cache line
<
< http://archives.postgresql.org/pgsql-hackers/2005-10/msg00498.php
|
|
|
|
|
|
|
| |
<
< * Add support for WIN1253 (Greek) encoding
<
< http://archives.postgresql.org/pgsql-bugs/2005-12/msg00000.php
|
|
|
|
|
|
|
| |
>
> * Add support for WIN1253 (Greek) encoding
>
> http://archives.postgresql.org/pgsql-bugs/2005-12/msg00000.php
|
|
|
|
| |
> http://archives.postgresql.org/pgsql-patches/2005-11/msg00173.php
|
|
|
|
|
|
|
| |
>
> * Consider increasing internal areas when shared buffers is increased
>
> http://archives.postgresql.org/pgsql-hackers/2005-10/msg01419.php
|
|
|
|
|
|
|
| |
<
< o Properly mark all libpq-exported functions with "PQ"
<
< http://archives.postgresql.org/pgsql-hackers/2005-10/msg00696.php
|
|
|
|
|
|
| |
< * Improve the information schema to be more standards-compliant:
<
< http://archives.postgresql.org/pgsql-bugs/2005-10/msg00028.php
|
|
|
|
|
|
|
| |
>
> o Properly mark all libpq-exported functions with "PQ"
>
> http://archives.postgresql.org/pgsql-hackers/2005-10/msg00696.php
|
|
|
|
|
|
|
|
| |
>
> * Consider padding the spinlock structure to have spinlock registers
> on different CPU cache line
>
> http://archives.postgresql.org/pgsql-hackers/2005-10/msg00498.php
|
|
|
|
|
|
|
|
| |
>
> * Fix ILIKE and regular expressions to handle case insensitivity
> properly in multibyte encodings
>
> http://archives.postgresql.org/pgsql-bugs/2005-10/msg00001.php
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
<
< o Add new version of PQescapeString() that doesn't double backslashes
< that are part of a client-only multibyte sequence
<
< Single-quote is not a valid byte in any supported client-only
< encoding. This requires using mblen() to determine if the
< backslash is inside or outside a multi-byte sequence.
<
< o Add new version of PQescapeString() that doesn't double
< backslashes when standard_conforming_strings is true and
< non-E strings are used
|
|
|
|
| |
> o -Port contrib/xml2
|
|
|
|
|
|
|
|
|
|
|
|
| |
> * Improve the information schema to be more standards-compliant:
>
> http://archives.postgresql.org/pgsql-bugs/2005-10/msg00028.php
> * Add URL to more complete multi-byte regression tests
>
> http://archives.postgresql.org/pgsql-hackers/2005-07/msg00272.php
< * Add URL to more complete multi-byte regression tests
<
< http://archives.postgresql.org/pgsql-hackers/2005-07/msg00272.php
|