Alvaro Herrera wrote:
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Maybe we could forcibly activate the freeze mode on a template database?
Might not be a bad idea. And even more to the point, forcibly disable
analyze.
Patch implementing this (albeit untested!)
Alvaro Herrera [EMAIL PROTECTED] writes:
Ok, it does what it's intended to do. But in testing it I also
confirmed that a database-wide vacuum creates a pgstat entry for it and
for all tables in it. Is this something we want to prevent?
That's odd, because I didn't see any such thing when I
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Ok, it does what it's intended to do. But in testing it I also
confirmed that a database-wide vacuum creates a pgstat entry for it and
for all tables in it. Is this something we want to prevent?
That's odd, because I didn't see
Alvaro Herrera [EMAIL PROTECTED] writes:
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Ok, it does what it's intended to do. But in testing it I also
confirmed that a database-wide vacuum creates a pgstat entry for it and
for all tables in it. Is this something we want to