Fujii Masao

to be initialized with proper values. Affected parameters are
fillfactor, analyze_threshold, and analyze_scale_factor.

Especially uninitialized fillfactor caused inefficient page usage
because we built a StdRdOptions struct in which fillfactor is zero
if any reloption is set for the toast table.

In addition, we disallow toast.autovacuum_analyze_threshold and
toast.autovacuum_analyze_scale_factor because we didn't actually
support them; they are always ignored.

Report by Rumko on pgsql-bugs on 12 May 2010.
Analysis by Tom Lane and Alvaro Herrera. Patch by me.

Backpatch to 8.4.

Almost all of the terms in docs and messages were replaced, but still
remains in a few comments and README files in codes.

Per gripe from Frank van Vugt.

While the values were correctly returned they were not moved into C variables
as they should be.

Closes: #5489

tag 9.0beta2

been written out from shared memory, but the previous phrasing might be read
to say that we send only what's been fsync'd.

and current server clock time to SR data messages.  These are not currently
used on the slave side but seem likely to be useful in future, and it'd be
better not to change the SR protocol after release.  Per discussion.
Also do some minor code review and cleanup on walsender.c, and improve the
protocol documentation.

When referring to postgresql.conf syntax, then it's without quotes
(wal_level=archive); in narrative it's with double quotes.  But never
single quotes.

per recent unintended-initdb-forcing fiasco

--enable-ssl -> --with-openssl

Now long names are adjusted with truncate_identifier() and NOTICE messages
are raised if names are actually truncated.

Backported to release 8.0.

Fujii Masao.  Review by Heikki Linnakangas and myself.

Tim Landscheidt

overlaps.

David Fetter

Fujii Masao

release notes.

Craig Ringer

Greg Sabino Mullane

details from Alvaro Herrera.

performed by "EXECUTE ... INTO".

Jaime Casanova

per Josh Berkus.  Add ALTER DATABASE to the "see also" section, too.

them off.

Josh Berkus, with slight wording changes by me.

This was broken by my previous patch to send WAL in smaller batches.

Patch by Fujii Masao.

We must filter out hashtable entries with frequencies less than those
specified by the algorithm, else we risk emitting junk entries whose
actual frequency is much less than other lexemes that did not get
tabulated.  This is bad enough by itself, but even worse is that
tsquerysel() believes that the minimum frequency seen in pg_statistic is a
hard upper bound for lexemes not included, and was thus underestimating
the frequency of non-MCEs.

Also, set the threshold frequency to something with a little bit of theory
behind it, to wit assume that the input distribution is approximately
Zipfian.  This might need adjustment in future, but some preliminary
experiments suggest that it's not too unreasonable.

Back-patch to 8.4, where this code was introduced.

Jan Urbanski, with some editorialization by Tom