Ooops...I accidentally took this off list, as Kevin was nice enough to point
out.
What am I looking for?
Outliers.
Yeah. It's just those 2. I'd assume that the db I created
yesterday would be an outlier, but template0 has been there all along
(of course) and is still listed as 648, a
On Thu, Mar 10, 2011 at 07:01:10AM -0600, Scott Whitney wrote:
Ooops...I accidentally took this off list, as Kevin was nice enough to point
out.
What am I looking for?
Outliers.
Yeah. It's just those 2. I'd assume that the db I created
yesterday would be an outlier, but
Ooops...I accidentally took this off list, as Kevin was nice enough
to point out.
What am I looking for?
Outliers.
Yeah. It's just those 2. I'd assume that the db I created
yesterday would be an outlier, but template0 has been there all
along (of course) and is still
On Thu, Mar 10, 2011 at 07:56:26AM -0600, Scott Whitney wrote:
If you have hardware problems like that you have way more problems.
You could have corruption (silent) occurring in any of the other
database files. Good luck.
I am, in fact, aware of that, but every single machine ever
On Thu, Mar 10, 2011 at 07:56:26AM -0600, Scott Whitney wrote:
If you have hardware problems like that you have way more
problems. You could have corruption (silent) occurring in any of
the other
database files. Good luck.
I am, in fact, aware of that, but every single machine
On Thu, Mar 10, 2011 at 08:18:34AM -0600, Scott Whitney wrote:
On Thu, Mar 10, 2011 at 07:56:26AM -0600, Scott Whitney wrote:
If you have hardware problems like that you have way more
problems. You could have corruption (silent) occurring in any of
the other
database files.
If you have hardware problems like that you have way more
problems. You could have corruption (silent) occurring in any
of the other
database files. Good luck.
I am, in fact, aware of that, but every single machine ever
manufactured will have hardware problems such
Scott Whitney sc...@journyx.com wrote:
This is also interesting. I just allowed connections to template0
for the express purpose of vacuuming it, did a full vac on
template0, and that did NOT clear up the hanging clogs.
Was it a VACUUM FREEZE followed by a CHECKPOINT? Did you also cover
This is also interesting. I just allowed connections to template0
for the express purpose of vacuuming it, did a full vac on
template0, and that did NOT clear up the hanging clogs.
Was it a VACUUM FREEZE followed by a CHECKPOINT? Did you also cover
that new database?
Yes, yes and yes,
Scott Whitney sc...@journyx.com wrote:
vacuumdb -f -v -z -F template0
VACUUM FULL (the -f option) is almost always a bad idea, for many
reasons. I wouldn't be surprised if it somehow messed you up.
I would schedule a database REINDEX on any databases where you used
the -f option, and then
I had this issue back in pg 7.x, and it was resolved by using -a in vacuumdb.
I'm having it again in v8.4.4.
So, my pg_clog directory contains files going back to Jul 13 of 2010.
Every Saturday, I run:
vacuumdb -a -v -F
I _thought_ that was supposed to clear those out. Am I wrong?
Scott Whitney sc...@journyx.com wrote:
my pg_clog directory contains files going back to Jul 13 of 2010.
Every Saturday, I run:
vacuumdb -a -v -F
I _thought_ that was supposed to clear those out. Am I wrong?
SELECT datname, datfrozenxid FROM pg_database;
to see which database
12 matches
Mail list logo
