user/sven/postgresql.git

Age	Commit message (Collapse)	Author
2014-01-07	Update copyright for 2014	Bruce Momjian
	Update all files in head, and files COPYRIGHT and legal.sgml in all back branches.
2013-10-24	Fix typos in comments.	Heikki Linnakangas

2013-06-01	Minor spelling fixes	Stephen Frost
	Fix a few spelling mistakes. Per bug report #8193 from Lajos Veres.
2013-05-29	pgindent run for release 9.3	Bruce Momjian
	This is the first run of the Perl-based pgindent script. Also update pgindent instructions.
2013-04-09	Remove duplicate initialization in XLogReadRecord.	Robert Haas
	Per a note from Dickson S. Guedes.
2013-01-18	Use the right timeline when beginning to stream from master.	Heikki Linnakangas
	The xlogreader refactoring broke the logic to decide which timeline to start streaming from. XLogPageRead() uses the timeline history to check which timeline the requested WAL position falls into. However, after the refactoring, XLogPageRead() is always first called with the first page in the segment, to verify the segment header, and only then with the actual WAL position we're interested in. That first read of the segment's header made XLogPageRead() to always start streaming from the old timeline containing the segment header, not the timeline containing the actual record, if there was a timeline switch within the segment. I thought I fixed this yesterday, but that fix was too narrow and only fixed this for the corner-case that the timeline switch happened in the first page of the segment. To fix this more robustly, pass explicitly the position of the record we're actually interested in to XLogPageRead, and use that to decide which timeline to read from, rather than deduce it from the page and offset. Per report from Fujii Masao.
2013-01-17	When xlogreader asks the callback function to read a page, make sure we	Heikki Linnakangas
	get a large enough part of the page to include the beginning of the next record we're interested in. The XLogPageRead callback uses the requested length to decide which timeline to stream WAL from, and if the first call is short, and the page contains a timeline switch, we'll repeatedly try to stream that page from the old timeline, and never get across the timeline switch.
2013-01-17	Fix a couple of error-handling bugs in the xlogreader patch.	Heikki Linnakangas
	XLogReadRecord should reset its state on every error, to make sure it re-reads the page on next call. It was inconsistent in that some errors did that, but some did not. In ReadRecord(), don't give up on an error if we're in standby mode. The loop was set up to retry, but the checks within the loop broke out of the loop on any error. Andres Freund, with some tweaking by me.
2013-01-16	Split out XLog reading as an independent facility	Alvaro Herrera
	This new facility can not only be used by xlog.c to carry out crash recovery, but also by external programs. By supplying a function to read XLog pages from somewhere, all the WAL reading can be used for completely different purposes. For the standard backend use, the behavior should be pretty much the same as previously. As for non-backend programs, an hypothetical pg_xlogdump program is now closer to reality, but some more backend support is still necessary. This patch was originally submitted by Andres Freund in a different form, but Heikki Linnakangas opted for and authored another design of the concept. Andres has advanced the patch since Heikki's initial version. Review and some (mostly cosmetics) changes by me.