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.

recover from elog(ERROR).  Problem was created by introduction of hash seq
search tracking awhile back, and affects all branches that have bgwriter;
in HEAD the disease has snuck into autovacuum and walwriter too.  (Not sure
that the latter two use hash_seq_search at the moment, but surely they might
someday.)  Per report from Sergey Koposov.

dynahash.c.  Sergey Koposov's current open problem shows the possible
usefulness of this, and it doesn't add much code.

(ts_rank_cd). Use palloc'ed array in ranking instead of flag.

Backpatch is needed for contrib version.

Rename synonym.syn.sample and thesaurs.ths.sample to
synonym_sample.syn and thesaurs_sample.ths accordingly to be able to use they
in regression test.

Ispell dictionary uses synthetic simple dictionary files.

It will be mush better to reimplement ts_debug in C (instead of SQL as now),
but it's planned for the future.

* Defined new struct WordEntryPosVector that holds a uint16 length and a
variable size array of WordEntries. This replaces the previous
convention of a variable size uint16 array, with the first element
implying the length. WordEntryPosVector has the same layout in memory,
but is more readable in source code. The POSDATAPTR and POSDATALEN
macros are still used, though it would now be more readable to access
the fields in WordEntryPosVector directly.

* Removed needfree field from DocRepresentation. It was always set to false.

* Miscellaneous other commenting and refactoring

for consistency with other column names such as in pg_stat_database.

transaction, unless rolled back or overridden by a SET clause for the same
variable attached to a surrounding function call.  Per discussion, these
seem the best semantics.  Note that this is an INCOMPATIBLE CHANGE: in 8.0
through 8.2, SET LOCAL's effects disappeared at subtransaction commit
(leading to behavior that made little sense at the SQL level).

I took advantage of the opportunity to rewrite and simplify the GUC variable
save/restore logic a little bit.  The old idea of a "tentative" value is gone;
it was a hangover from before we had a stack.  Also, we no longer need a stack
entry for every nesting level, but only for those in which a variable's value
actually changed.

database-wide editions.

Per report from bitsandbytes88 <at> hotmail.com and subsequent discussion.

vacuum, instead of waiting till commit.