| Age | Commit message (Collapse) | Author |
|---|
|
Riggs, additional code and docs by me. Per discussion.
|
|
win32.mak file.
Enable building with kerberos support using the win32.mak file.
Hiroshi Saito + me
|
|
< o -Add MOVE
< o -Add support for SCROLL cursors
> o Add support for MOVE and SCROLL cursors
|
|
Make it possible to set the default from builenv.bat.
Per request from Dave Page
|
|
Backpatch doc change to 8.2.X.
|
|
multi-byte value. It can also be a single-byte encoded character if
the client and server versions match.
Backpatch to 8.2.X.
|
|
< o -Add support for WITH HOLD and SCROLL cursors
> o -Add support for SCROLL cursors
> o Add support for WITH HOLD cursors
|
|
< o Add support for WITH HOLD and SCROLL cursors
> o -Add support for WITH HOLD and SCROLL cursors
|
|
< o Add MOVE
> o -Add MOVE
|
|
< Currently all schemas are owned by the super-user because they are
< copied from the template1 database.
> Currently all schemas are owned by the super-user because they are copied
> from the template1 database. However, since all objects are inherited
> from the template database, it is not clear that setting schemas to the db
> owner is correct.
|
|
< * %Set proper permissions on non-system schemas during db creation
> * Set proper permissions on non-system schemas during db creation
|
|
|
|
processes to be running simultaneously. Also, now autovacuum processes do not
count towards the max_connections limit; they are counted separately from
regular processes, and are limited by the new GUC variable
autovacuum_max_workers.
The launcher now has intelligence to launch workers on each database every
autovacuum_naptime seconds, limited only on the max amount of worker slots
available.
Also, the global worker I/O utilization is limited by the vacuum cost-based
delay feature. Workers are "balanced" so that the total I/O consumption does
not exceed the established limit. This part of the patch was contributed by
ITAGAKI Takahiro.
Per discussion.
|
|
Pavel Stehule, reworked a bit by Tom.
|
|
access to the planner's cursor-related planning options, and provide new
FETCH/MOVE routines that allow access to the full power of those commands.
Small refactoring of planner(), pg_plan_query(), and pg_plan_queries()
APIs to make it convenient to pass the planning options down from SPI.
This is the core-code portion of Pavel Stehule's patch for scrollable
cursor support in plpgsql; I'll review and apply the plpgsql changes
separately.
|
|
"Server-side support of all encodings" around 2007/3/26.
initdb required.
|
|
< o Consider reducing on-disk varlena length from four to two
< because a heap row cannot be more than 64k in length
> o Consider reducing on-disk varlena length from four bytes to
> two because a heap row cannot be more than 64k in length
|
|
|
|
EXPLAIN ANALYZE can sometimes be significantly slower than running
the same query normally, and make some minor markup improvements.
|
|
ref page (sorry, my fault!), and simplify the coding of
ResetTempTableNamespace().
|
|
> * -Add RESET SESSION command to reset all session state
|
|
reviewed by Neil Conway. This patch adds the following DDL command
variants: RESET SESSION, RESET TEMP, RESET PLANS, CLOSE ALL, and
DEALLOCATE ALL. RESET SESSION is intended for use by connection
pool software and the like, in order to reset a client session
to something close to its initial state.
Note that while most of these command variants can be executed
inside a transaction block (but are not transaction-aware!),
RESET SESSION cannot. While this is inconsistent, it is intended
to catch programmer mistakes: RESET SESSION in an open transaction
block is probably unintended.
|
|
< o Allow single-byte header storage for arrays
> o Allow single-byte header storage for array elements
|
|
> o Allow single-byte header storage for arrays
|
|
> o Have WITH CONSTRAINTS also create constraint indexes
> http://archives.postgresql.org/pgsql-patches/2007-04/msg00149.php
|
|
* Simplify ability to create partitioned tables
> http://archives.postgresql.org/pgsql-hackers/2007-04/msg00151.php
|
|
> o -Make CLUSTER preserve recently-dead tuples per MVCC requirements
|
|
|
|
> o -Add more logical syntax CLUSTER table USING index;
|
|
Holger Schurig
|
|
|
|
|
|
|
|
confusion.
|
|
Michael Fuhr
|
|
> * -Allow use of indexes to search for NULLs
|
|
o -Support a smaller header for short variable-length fields
|
|
Teodor Sigaev, with some kibitzing from Tom Lane.
|
|
types.
|
|
This commit breaks any code that assumes that the mere act of forming a tuple
(without writing it to disk) does not "toast" any fields. While all available
regression tests pass, I'm not totally sure that we've fixed every nook and
cranny, especially in contrib.
Greg Stark with some help from Tom Lane
|
|
* Reduce WAL traffic so only modified values are written rather than
entire rows
>
> http://archives.postgresql.org/pgsql-hackers/2007-03/msg01589.php
>
|
|
installation.
|
|
<H3 id="item3.7">3.7) What computer hardware should I use?</H3>
|
|
CONCURRENTLY.
Gregory Stark
|
|
> o -Allow PL/PythonU to return boolean rather than 1/0
|
|
Add the latter to the values checked in pg_control, since it can't be changed
without invalidating toast table content. This commit in itself shouldn't
change any behavior, but it lays some necessary groundwork for experimentation
with these toast-control numbers.
Note: while TOAST_TUPLE_THRESHOLD can now be changed without initdb, some
thought still needs to be given to needs_toast_table() in toasting.c before
unleashing random changes.
|
|
< * Add transaction_idle_timeout GUC so locks are not held for long
> * Add idle_in_transaction_timeout GUC so locks are not held for long
|
|
< * Add idle_timeout GUC so locks are not held for log periods of time
> * Add transaction_idle_timeout GUC so locks are not held for long
> periods of time
|
|
> * Allow all data types to cast to and from TEXT
>
> http://archives.postgresql.org/pgsql-hackers/2007-04/msg00017.php
>
>
|
|
>
> * Add idle_timeout GUC so locks are not held for log periods of time
|
