| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Mark Woodward <pgsql(at)mohawksoft(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Zdenek Kotala <zdenek(dot)kotala(at)sun(dot)com>, Koichi Suzuki <suzuki(dot)koichi(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: How to avoid transaction ID wrap |
| Date: | 2006-06-07 23:00:33 |
| Message-ID: | 20060607230033.GH45331@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 07, 2006 at 07:07:55PM -0400, Mark Woodward wrote:
> I guess what I am saying is that PostgreSQL isn't "smooth," between
> checkpoints and vacuum, it is near impossible to make a product that
> performs consistently under high load.
Have you tuned the bgwriter and all the vacuum_cost stuff? I've get to
find a case where I couldn't smooth out the IO load so that it wasn't an
issue.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Woodward | 2006-06-07 23:07:55 | Re: How to avoid transaction ID wrap |
| Previous Message | Jim C. Nasby | 2006-06-07 22:45:30 | Re: How to avoid transaction ID wrap |