Generated Changelog since last Beta ...

upgrade version to beta6

Sorry Eiji.

O_SYNC, or O_DSYNC (as available on a given platform).  Add GUC parameter
to control sync method.
Also, add defense to XLogWrite to prevent it from going nuts if passed
a target write position that's past the end of the buffers so far filled
by XLogInsert.

because we need page LSNs stored in the main database to be less than
the current XLOG position.  Hence, generate the new XLOG segment at last
old segment number plus one.

	Provide an extenisible scheme of encoding conversion.
	As the first step, SJIS and BIG5 are supported.
	From now on multibyte people would be happy to use
	this psqlodbc driver.

Eiji Tokuya e-tokuya@mail.sankyo-unyu.co.jp

Fix a bug where cs.execute('select %d + %d', (1, 2)) would get interpreted
as cs.executemany('select %d + %d', (1, 2))

to a join or subselect alias ... cf. Oliver Elphick's complaint 13-Mar.

is still a memory leak, but a little less bad than it was.

I'm not sure that it's really necessary to save insert events when there
are only after update or delete triggers, but certainly it's wrong for
COPY to behave differently from an INSERT query.

does have -o.

bug reports.  ;-)

(per recent discussion with Tatsuo).  Hopefully the compilers with
that old bug are all long gone.

Change the administrator to 'an' administrator.

prevent disguised failures.

Just try again later.

	This connection has been terminated by the administrator

Could do with more testing, but it works in the simple cases.

pg_ctl '-l' option.

detect case that next page in log came from an older run than the prior
page.  This avoids the necessity to re-zero the log after recovery from
a crash, which is good because we need not risk destroying valuable log
information.
This forces another initdb since yesterday :-(.  Need to get that log
reset utility done...