delta/postgresql.git, branch REL9_0_ALPHA4 git.postgresql.org: git/postgresql.git Version stamp 9.0alpha4 2010-02-19T18:43:31+00:00 Peter Eisentraut peter_e@gmx.net 2010-02-19T18:43:31+00:00 3ba6a3cb76f3c3ab2994d83c84ec5fa453d40aa8 (in the right branch) 
(in the right branch)
Document --version and --help options for all client applications (they 2010-02-19T14:36:45+00:00 Bruce Momjian bruce@momjian.us 2010-02-19T14:36:45+00:00 f8f0140d73b23b92062465c4977a71a6ee336eea all support it). Per report from Josh Kupershmidt 
all support it).

Per report from Josh Kupershmidt
Small corrections to message output targets in pg_ctl 2010-02-19T14:12:19+00:00 Peter Eisentraut peter_e@gmx.net 2010-02-19T14:12:19+00:00 4c6c6b52d27fa60ddb287efb194ae77ee9385248 - The message "server stopped" should be affected by the -s option, just like "server started" already was. - The message "could not start server" should consistently go to stderr. 
- The message "server stopped" should be affected by the -s option, just
  like "server started" already was.

- The message "could not start server" should consistently go to stderr.
Don't use O_DIRECT when writing WAL files if archiving or streaming is 2010-02-19T10:51:04+00:00 Heikki Linnakangas heikki.linnakangas@iki.fi 2010-02-19T10:51:04+00:00 ad458cfe81bcefd6d8bd17ff2e42c6599d441bd6 enabled. Bypassing the kernel cache is counter-productive in that case, because the archiver/walsender process will read from the WAL file soon after it's written, and if it's not cached the read will cause a physical read, eating I/O bandwidth available on the WAL drive. Also, walreceiver process does unaligned writes, so disable O_DIRECT in walreceiver process for that reason too. 
enabled. Bypassing the kernel cache is counter-productive in that case,
because the archiver/walsender process will read from the WAL file
soon after it's written, and if it's not cached the read will cause
a physical read, eating I/O bandwidth available on the WAL drive.

Also, walreceiver process does unaligned writes, so disable O_DIRECT
in walreceiver process for that reason too.
Forbid setval() during recovery. This prevents the PANIC reported by 2010-02-19T06:29:19+00:00 Heikki Linnakangas heikki.linnakangas@iki.fi 2010-02-19T06:29:19+00:00 94f610b16342d7727774f6bb9245341cfa6f895c Erik Rijkers. Patch by Andres Freund. 
Erik Rijkers. Patch by Andres Freund.
First pass over client applications documentation proofreading. 2010-02-19T03:50:03+00:00 Bruce Momjian bruce@momjian.us 2010-02-19T03:50:03+00:00 2f6b4560afc6ab51b82f88b111041030b3a7329e gabrielle 
gabrielle
Remove mention that binary distributions pre-compile the tutorial files. 2010-02-19T01:15:54+00:00 Bruce Momjian bruce@momjian.us 2010-02-19T01:15:54+00:00 4e3a616355a8025c8d9099891fc1352c940088f1 






Fix STOP WAL LOCATION in backup history files no to return the next
2010-02-19T01:04:03+00:00

Itagaki Takahiro
itagaki.takahiro@gmail.com

2010-02-19T01:04:03+00:00

3230fd056afd4e056c2a78d569c90446c73051b8

segment of XLOG_BACKUP_END record even if the the record is placed
at a segment boundary. Furthermore the previous implementation could
return nonexistent segment file name when the boundary is in segments
that has "FE" suffix; We never use segments with "FF" suffix.

Backpatch to 8.0, where hot backup was introduced.

Reported by Fujii Masao.





segment of XLOG_BACKUP_END record even if the the record is placed
at a segment boundary. Furthermore the previous implementation could
return nonexistent segment file name when the boundary is in segments
that has "FE" suffix; We never use segments with "FF" suffix.

Backpatch to 8.0, where hot backup was introduced.

Reported by Fujii Masao.







Translation updates for 9.0alpha4
2010-02-19T00:40:05+00:00

Peter Eisentraut
peter_e@gmx.net

2010-02-19T00:40:05+00:00

a39f02e36963897feed8c0c93fc96f8e3657405c












Preliminary release notes for 9.0alpha4
2010-02-19T00:35:18+00:00

Peter Eisentraut
peter_e@gmx.net

2010-02-19T00:35:18+00:00

1222296768aa93f9b6eee7000feddb86ab0ecd69