| From: | Scott Whitney <scott(at)journyx(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Scott Whitney <swhitney(at)journyx(dot)com>, pgsql-admin(at)postgresql(dot)org, Kenneth Marshall <ktm(at)rice(dot)edu> |
| Subject: | Re: pg_clogs hanging around |
| Date: | 2011-03-10 15:47:24 |
| Message-ID: | 7423332.14202.1299772044088.JavaMail.root@zimbra.int.journyx.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> > 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, actually. Unless I did it wrong, which is always a strong possibility. Especially early in the morning...
pg statement: update pg_database set datallowconn=true where datname='template0';
shell: vacuumdb -f -v -z -F template0
pg statement: checkpoint;
pg statement: update pg_database set datallowconn=true where datname='template0';
Like I said, I'm beginning to believe that something is rotten wrt my Saturday vacs...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2011-03-10 15:56:50 | Re: pg_clogs hanging around |
| Previous Message | Kevin Grittner | 2011-03-10 15:30:44 | Re: pg_clogs hanging around |