- 16 6月, 2006 10 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
close. ITAGAKI Takahiro
-
由 Bruce Momjian 提交于
less than one row is returned by the SELECT, for Oracle PL/SQL compatibility. Improve SELECT INTO documentation. Matt Miller
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
non-PostgreSQL libraries cannot be loaded using this capability.
-
由 Bruce Momjian 提交于
< get_employee_salary(emp_id => 12345, tax_year => 2001) > get_employee_salary(emp_id AS 12345, tax_year AS 2001)
-
由 Bruce Momjian 提交于
description. Nis Jorgensen
-
由 Bruce Momjian 提交于
> > o Fix memory leak from exceptions > > http://archives.postgresql.org/pgsql-performance/2006-06/msg00305.php
-
由 Bruce Momjian 提交于
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
-
由 Bruce Momjian 提交于
> o Allow PL/PgSQL RETURN to return row or record functions > > http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php
-
- 15 6月, 2006 27 次提交
-
-
由 Bruce Momjian 提交于
< < * Consider padding the spinlock structure to have spinlock registers < on different CPU cache line < < http://archives.postgresql.org/pgsql-hackers/2005-10/msg00498.php
-
由 Tom Lane 提交于
remove the infrastructure needed to enforce the limit, ie, the global LRU list of cache entries. On small-to-middling databases this wins because maintaining the LRU list is a waste of time. On large databases this wins because it's better to keep more cache entries (we assume such users can afford to use some more per-backend memory than was contemplated in the Berkeley-era catcache design). This provides a noticeable improvement in the speed of psql \d on a 10000-table database, though it doesn't make it instantaneous. While at it, use per-catcache settings for the number of hash buckets per catcache, rather than the former one-size-fits-all value. It's a bit silly to be using the same number of hash buckets for, eg, pg_am and pg_attribute. The specific values I used might need some tuning, but they seem to be in the right ballpark based on CATCACHE_STATS results from the standard regression tests.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
< < * Add support for WIN1253 (Greek) encoding < < http://archives.postgresql.org/pgsql-bugs/2005-12/msg00000.php
-
由 Bruce Momjian 提交于
> > * Add support for WIN1253 (Greek) encoding > > http://archives.postgresql.org/pgsql-bugs/2005-12/msg00000.php
-
由 Bruce Momjian 提交于
> > * Consider increasing internal areas when shared buffers is increased > > http://archives.postgresql.org/pgsql-hackers/2005-10/msg01419.php
-
由 Bruce Momjian 提交于
< < o Properly mark all libpq-exported functions with "PQ" < < http://archives.postgresql.org/pgsql-hackers/2005-10/msg00696.php
-
由 Bruce Momjian 提交于
< * Improve the information schema to be more standards-compliant: < < http://archives.postgresql.org/pgsql-bugs/2005-10/msg00028.php
-
由 Bruce Momjian 提交于
> > o Properly mark all libpq-exported functions with "PQ" > > http://archives.postgresql.org/pgsql-hackers/2005-10/msg00696.php
-
由 Bruce Momjian 提交于
> > * Consider padding the spinlock structure to have spinlock registers > on different CPU cache line > > http://archives.postgresql.org/pgsql-hackers/2005-10/msg00498.php
-
由 Bruce Momjian 提交于
> > * Fix ILIKE and regular expressions to handle case insensitivity > properly in multibyte encodings > > http://archives.postgresql.org/pgsql-bugs/2005-10/msg00001.php
-
由 Bruce Momjian 提交于
< < 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
-
由 Bruce Momjian 提交于
> o -Port contrib/xml2
-
由 Bruce Momjian 提交于
> * 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
-
由 Bruce Momjian 提交于
> > o Add API for 64-bit large object access > > http://archives.postgresql.org/pgsql-hackers/2005-09/msg00781.php
-
由 Bruce Momjian 提交于
< o %Allow pg_dump to use multiple -t and -n switches > o %Allow pg_dump to use multiple -t and -n switches [pg_dump]
-
由 Bruce Momjian 提交于
< o %Allow pg_dump to use multiple -t and -n switches [pg_dump] > o %Allow pg_dump to use multiple -t and -n switches > > http://archives.postgresql.org/pgsql-patches/2006-01/msg00190.php >
-
由 Bruce Momjian 提交于
< Right now only one encoding is allowed per database. > Right now only one encoding is allowed per database. [locale] > * Add CREATE COLLATE? [locale]
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
< o Check WSACancelBlockingCall() for interrupts (win32intr) > o Check WSACancelBlockingCall() for interrupts [win32intr]
-
由 Bruce Momjian 提交于
> o Fix problem when cascading referential triggers make changes on > cascaded tables, seeing the tables in an intermediate state > > http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php > http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php
-
由 Bruce Momjian 提交于
> > * Add URL to more complete multi-byte regression tests > > http://archives.postgresql.org/pgsql-hackers/2005-07/msg00272.php
-
由 Bruce Momjian 提交于
> * Allow user-defined types to accept 'typmod' parameters > http://archives.postgresql.org/pgsql-hackers/2005-08/msg01142.php > http://archives.postgresql.org/pgsql-hackers/2005-09/msg00012.php
-
由 Tom Lane 提交于
the lower-level large object functions fails, it will have already set a suitable error message --- probably something from the backend --- and it is not useful to overwrite that with a generic 'error while reading large object' message. So remove redundant messages.
-
由 Tom Lane 提交于
places --- that risks corrupting data structures, losing sync with the backend, etc. We now longjmp only from calls to readline, fgets, and fread, which we assume are coded to protect themselves against interrupts at undesirable times. This requires adding explicit tests for cancel_pressed in long-running loops, but on the whole it's far cleaner. Martijn van Oosterhout and Tom Lane.
-
- 14 6月, 2006 3 次提交
-
-
由 Tom Lane 提交于
Problems noted while experimenting with new control-C code for psql.
-
由 Tom Lane 提交于
function call. Previously, there may have been no CHECK_FOR_INTERRUPTS at all in the fastpath code path, making it impossible to cancel an operation such as \lo_import externally. This addition doesn't ensure you can cancel, since your SIGINT may arrive while the backend is idle waiting for the client, but it gives the largest window we can easily provide. Noted while experimenting with new control-C code for psql.
-
由 Bruce Momjian 提交于
< o %Add CSV output format
-