Quoting Tom Lane [EMAIL PROTECTED]:
I fear we still have to disable full_page_writes (force it ON) if
XLogArchivingActive is on. Comments?
Yeah - if you are enabling PITR, then you care about safety and integrity, so it
makes sense (well, to me anyway).
Cheers
Mark
Quoting Bruce Momjian [EMAIL PROTECTED]:
Yep, related. There was a typo in win32.h for lstat that was exposed by
the new tablespace changes. I also added the proper parameters rather
than just redefining the symbol.
Attached is the patch. Do we need to repackage beta2 for this? Tom did
Certainly gave me a chuckle. Technical documentation with humour...now the
product has *everything*.
Mark
Quoting Tom Lane [EMAIL PROTECTED]:
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
I love this:
The ability to restore the database to a previous point in time creates
some
Quoting Bruce Momjian [EMAIL PROTECTED]:
Mark Kirkwood wrote:
I was wondering about this point - might it not be just as reasonable
for the copied file to *be* an exact image of pg_control? Then a very
simple variant of pg_controldata (or maybe even just adding switches to
Hmm. Which file(s) were growing, exactly? How many row updates is this
run covering?
The toast table gets about 90 percent of the growth, followed by the toast
index at about 9 percent. The actual table + primary key stay at about 2M each.
I neglected to mention what the update
