| From: | Ryan Mahoney <ryan(at)paymentalliance(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: max_fsm_pages |
| Date: | 2003-12-05 16:48:59 |
| Message-ID: | 1070642939.8567.161.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> In previous versions you're kind of on your own :-(
Hmmm, in this case we need to use 7.3.2 because is it the only supported
postgres version from the application vendor. In 7.3.2, Vacuum tells
me:
INFO: Pages 248: Changed 0, reaped 244, Empty 0, New 0; Tup 4464: Vac
0, Keep/VTL 0/0, UnUsed 1644, MinLen 184, MaxLen 571; Re-using:
Free/Avail. Space 33436/19528; EndEmpty/Avail. Pages 0/47
for each table. Can is sum one of those values across the databse - or
are they not really relevant to max_fsm_pages?
Thanks!
-r
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jason C. Pion | 2003-12-05 16:57:39 | Re: postgresql locks the whole table! |
| Previous Message | Keith C. Perry | 2003-12-05 16:46:28 | Re: Perl / mod_perl / PostgreSQL was: Good open source |