Scott Marlowe

instead of calling a bunch of individual functions.

This function can also be called directly, taking a PID as an argument, to
return only the data for a single PID.

< * Consider increasing the number of default statistics target, and
<   reduce statistics target overhead

< 	o Allow dictionary to filter out only stop words
> 	o Allow dictionaries to change the token that is passed on to
> 	  later dictionaries

        o Consider changing error to warning for strings larger than one
          megabyte

          http://archives.postgresql.org/pgsql-bugs/2008-02/msg00190.php
          http://archives.postgresql.org/pgsql-patches/2008-03/msg00062.php

than only 'off'.

Not clear that there's any observable bug at present from this omission,
but it seems like something to fix going forward.

to avoid the pain of manually renumbering them anytime we insert another
name in alphabetical order.  An excellent idea from Alex Hunsaker and
NikhilS' inherited-constraints patch --- whether or not the rest of that
gets in, this should.  Dunno why we never thought of it before.

file:

	http://www.postgresql.org/download

> * -Add function to report the time of the most recent server reload

> 	o -Improve display of enums to show valid enum values

standalone msvc build of libpq.

Hiroshi Saito

Hitoshi Harada

files were last loaded.

George Gensure

These changes assume that the varchar and xml data types are represented
the same as text.  (I did not, however, accept the portions of the proposed
patch that wanted to assume bytea is the same as text --- tgl.)

Brendan Jurd

Joshua Drake.

UPDATE/DELETE forgot to teach ruleutils.c to display the alias.
Per bug #4141 from Mathias Seiler.

support multiple OUT arguments, though.)

Hannu Krosing

any hardcoding of those options. Along the way, reorder the expression used to
calculate RELSEG_SIZE to make it slightly clearer. For now wal_segsize is only
allowed to have a value of 1 on Windows - we can relax that when we get full
large file support in the backend.

Pavel Stehule

retrieved to be controlled through a GUC variable.

Robert Hell

let XLOG_BLCKSZ and XLOG_SEG_SIZE be set via configure.  Per a proposal by
Mark Wong, though I thought it better to call the switches after "wal" rather
than "xlog".

Dickson S. Guedes

This has been the only documented and encouraged syntax for a long time, and
with extension facilities such as aliases being proposed, it is a good time to
clean up the legacy syntax a bit.

Author: Bernd Helmle <mailings@oopsware.de>

support for a nonsegmented mode from md.c.  Per recent discussions, there
doesn't seem to be much value in a "never segment" option as opposed to
segmenting with a suitably large segment size.  So instead provide a
configure-time switch to set the desired segment size in units of gigabytes.
While at it, expose a configure switch for BLCKSZ as well.

Zdenek Kotala

abbreviations.  It doesn't conflict with any other abbreviation
so there seems no reason not to include it.  Per a recent gripe.

it vary with BLCKSZ as before.  This agrees with what the documentation says,
and avoids a regression test problem when BLCKSZ is larger than default.
Per recent discussion.

a user-supplied TID is out of range for the relation.  This is needed to
preserve compatibility with our pre-8.3 behavior, and it is sensible anyway
since if the query were implemented by brute force rather than optimized
into a TidScan, the behavior for a non-existent TID would be zero rows out,
never an error.  Per gripe from Gurjeet Singh.