At Fri, 15 Jul 2005 14:39:36 -0600,
Ron Wills wrote:
I just wanted to thank everyone for their help. I believe we found a
solution that will help with this problem, with the hardware
configuration and caching the larger tables into smaller data sets.
A valuable lesson learned from this
At Fri, 15 Jul 2005 14:53:26 -0700,
Jeffrey W. Baker wrote:
>
> On Fri, 2005-07-15 at 15:29 -0600, Ron Wills wrote:
> > Here's a bit of a dump of the system that should be useful.
> >
> > Processors x2:
> >
> > vendor_id : AuthenticAMD
> &
At Fri, 15 Jul 2005 14:17:34 -0700,
Jeffrey W. Baker wrote:
>
> On Fri, 2005-07-15 at 15:04 -0600, Ron Wills wrote:
> > At Fri, 15 Jul 2005 13:45:07 -0700,
> > Joshua D. Drake wrote:
> > >
> > > Ron Wills wrote:
> > > > Hello all
> > > &g
At Fri, 15 Jul 2005 14:00:07 -0700,
Jeffrey W. Baker wrote:
>
> On Fri, 2005-07-15 at 14:39 -0600, Ron Wills wrote:
> > Hello all
> >
> > I'm running a postgres 7.4.5, on a dual 2.4Ghz Athlon, 1Gig RAM and
> > an 3Ware SATA raid. Currently the database is on
At Fri, 15 Jul 2005 13:45:07 -0700,
Joshua D. Drake wrote:
>
> Ron Wills wrote:
> > Hello all
> >
> > I'm running a postgres 7.4.5, on a dual 2.4Ghz Athlon, 1Gig RAM and
> > an 3Ware SATA raid.
>
> 2 drives?
> 4 drives?
> 8 drives?
3 dri
Hello all
I'm running a postgres 7.4.5, on a dual 2.4Ghz Athlon, 1Gig RAM and
an 3Ware SATA raid. Currently the database is only 16G with about 2
tables with 50+ row, one table 20+ row and a few small
tables. The larger tables get updated about every two hours. The
problem I having with
