>
> 	  Another idea would be to allow actual SELECT queries in a COPY.

in which invalid page data could be transiently written to disk by
concurrent bgwriter activity.  There doesn't seem any risk of loss of
actual user data, but an empty page could possibly be left corrupt if a
crash occurs before the correct data gets written out.  Pointed out by
Alvaro Herrera.

It uses existing macros instead of touching directly.

ITAGAKI Takahiro

>
> 	o Allow COPY to output from views
>

Greg Sabino Mullane

messages.

strings.  This is consistent with SQL conventions, and since Bruce
already changed initdb in a way that assumed it worked like this, seems
we'd better make it work like this.

given, per gripe from Michael Fuhr.

Per report from Cesar Paipilla.

by properly updating transaction state after AUTOCOMMIT.

<   This would be beneficial when there are few distinct values.
>   This would be beneficial when there are few distinct values.  This is
>   already used by GROUP BY.
946d946
< * Allow DISTINCT to use hashing like GROUP BY

Backpatch to 8.0.X.

< * Allow WAL traffic to be steamed to another server for stand-by
> * Allow WAL traffic to be streamed to another server for stand-by

> * Allow DISTINCT to use hashing like GROUP BY

> * Allow WAL traffic to be steamed to another server for stand-by
>   replication

< * Research use of sched_yield() for spinlock acquisition failure

>
1032a1034
> * Remove BeOS and QNX-specific code

> 	o Fix SELECT INTERVAL '1' MONTH

   errmsg("canceling query due to user request or statement timeout")));

Hiroshi Saito

Michael Fuhr

<
> * Update Bonjour to work with newer cross-platform SDK

tag it all beta2 ...

<
390d388
<
453c451
< 	  removed or have its heap and index files truncated.  One
> 	  be removed or have its heap and index files truncated.  One
< * Use a phantom command counter for nested subtransactions to reduce
<   per-tuple overhead

> 	o Add single-step debugging of PL/PgSQL functions

sake of brevity and clarity.

Make pg_reload_conf(), pg_rotate_logfile(), and pg_cancel_backend()
return a boolean rather than an integer to indicate success or failure.

Along the way, make some minor cleanups to dbsize.c -- in particular,
use elog() rather than ereport() for "shouldn't happen" error
conditions, and remove some of the more flagrant violations of the
Postgres indentation conventions.

Catalog version bumped.