Seems to have been introduced in 8.1 by careless SECS_PER_DAY
search-and-replace.

no-longer-needed pages at the end of a table.  We thought we could throw away
pages containing HEAPTUPLE_DEAD tuples; but this is not so, because such
tuples very likely have index entries pointing at them, and we wouldn't have
removed the index entries.  The problem only emerges in a somewhat unlikely
race condition: the dead tuples have to have been inserted by a transaction
that later aborted, and this has to have happened between VACUUM's initial
scan of the page and then rechecking it for empty in count_nondeletable_pages.
But that timespan will include an index-cleaning pass, so it's not all that
hard to hit.  This seems to explain a couple of previously unsolved bug
reports.

Jun Kuwamura

>
> 	o Prevent long-lived temporary tables from causing frozen-xid
> 	  advancement starvation
>
> 	  http://archives.postgresql.org/pgsql-general/2007-06/msg01645.php

>
> * Make it possible to use RETURNING together with conditional DO INSTEAD
>   rules, such as for partitioning setups
>
>   http://archives.postgresql.org/pgsql-hackers/2007-09/msg00577.php

Heikki Linnakangas

Kris Jurka

Andrew Maclean

Brendan Jurd

Fix markup in previous commit.

Albe Laurenz

don't need to recommend nightly analyzes anymore unless autovacuum is off.

Backpatch to 8.2.X.

Oleg.

* adds a few missing words to some commands (like adding GIN as a valid
index type or OWNED BY for ALTER SEQUENCE,...)

* support for ALTER TABLE foo ENABLE/DISABLE REPLICA TRIGGER/RULE

* autocomplete CREATE DATABASE foo TEMPLATE (mostly done to prevent
conflicts with the TEMPLATE keyword for text search)

* support for ALTER/CREATE/DROP TEXT SEARCH as well as COMMENT ON TEXT
SEARCH and the corresponding psql backslash commands.
This proved a little more difficult than expected due to the fact that
words_after_create[] is used for two purposes - one is to provide a list
of words that follow immediatly after CREATE (or DROP) and the other
purpose is to use it for autocompleting anywhere in the statement if the
word in that struct is found with a query.
Since TEXT SEARCH CONFIGURATION|DICTIONARY|TEMPLATE|PARSER results in 3
words instead of one (as all the other words in that list are) I added a
flag to the struct to tell create_command_generator() to skip that entry
 for autocompleting immediatly after CREATE which feels like a dirty
hack (but that holds true for a lot of code in tab-complete.c).


Stefan Kaltenbrunner

of PostgreSQL 8.2) and provides a link to compiling and linking section.

Euler Taveira de Oliveira

Backpatch to 8.2.X.

the problems non-root reading /etc/shadow.

contrib/intarray's GIN opclass override the built-in default.  Per bug #3048
and other complaints.

Fujii Masao

administrator-scheduled vacuums.

patch from  ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp>

Jun Kuwamura

who reported it privately to me.

than two independent bits (one of which was never used in heap pages anyway,
or at least hadn't been in a very long time).  This gives us flexibility to
add the HOT notions of redirected and dead item pointers without requiring
anything so klugy as magic values of lp_off and lp_len.  The state values
are chosen so that for the states currently in use (pre-HOT) there is no
change in the physical representation.

so that invalidly encoded data cannot enter the database by these means.

Jeremy Drake.

Per buildfarm and Teodor.

was removed.

switch, viz '-fno-alias'.  Since we have a separate code path here
anyway, it's just as easy to cooperate.