[resend, because of apparent failure to hit the list]
Bruce Momjian wrote:
I am dismayed that we are using a 16MB file for monitoring archive
activity. Can't you use pg_current_xlog_location() and only check
for an archive file when that location changes?
Hmmm Let me think about
Kevin Grittner wrote:
[resend, because of apparent failure to hit the list]
Bruce Momjian wrote:
I am dismayed that we are using a 16MB file for monitoring archive
activity. Can't you use pg_current_xlog_location() and only check
for an archive file when that location changes?
Fujii Masao wrote:
On Fri, Jan 15, 2010 at 12:50 AM, Bruce Momjian br...@momjian.us wrote:
Looking at the archive_timeout documentation and CheckArchiveTimeout(),
it appears we force a new xlog file and archive it even if no activity
has been recorded in the xlog file. ?Is this correct?
Kevin Grittner wrote:
Bruce Momjian br...@momjian.us wrote:
Looking at the archive_timeout documentation and
CheckArchiveTimeout(), it appears we force a new xlog file and
archive it even if no activity has been recorded in the xlog file.
Is this correct? Should we document this or
Looking at the archive_timeout documentation and CheckArchiveTimeout(),
it appears we force a new xlog file and archive it even if no activity
has been recorded in the xlog file. Is this correct? Should we
document this or fix it so only xlog files with contents are archived?
--
Bruce
Bruce Momjian br...@momjian.us wrote:
Looking at the archive_timeout documentation and
CheckArchiveTimeout(), it appears we force a new xlog file and
archive it even if no activity has been recorded in the xlog file.
Is this correct? Should we document this or fix it so only xlog
files
On Fri, Jan 15, 2010 at 12:50 AM, Bruce Momjian br...@momjian.us wrote:
Looking at the archive_timeout documentation and CheckArchiveTimeout(),
it appears we force a new xlog file and archive it even if no activity
has been recorded in the xlog file. Is this correct?
No. CheckArchiveTimeout()
