From: Mark Lewis <mark.lewis@mir3.com>
To: Todd Landfried <tlandfried@viatornetworks.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Needed: Simplified guide to optimal memory
Date: Thu, 16 Jun 2005 10:01:00 -0700
Message-ID: <1118941260.698.5.camel@archimedes.mirlogic.com> (raw)
In-Reply-To: <9A491A53-A5F5-4061-B1EA-8E4216299407@viatornetworks.com>
References: <Pine.LNX.4.44.0506151123510.1139-100000@zigo.dhs.org>
<2608.1118845105@sss.pgh.pa.us>
<9A491A53-A5F5-4061-B1EA-8E4216299407@viatornetworks.com>
We run the RPM's for RH 7.3 on our 7.2 install base with no problems.
RPM's as recent as for PostgreSQL 7.4.2 are available here:
ftp://ftp10.us.postgresql.org/pub/postgresql/binary/v7.4.2/redhat/redhat-7.3/
Or you can always compile from source. There isn't any such thing as a
'supported' package for RH7.2 anyway.
-- Mark Lewis
On Thu, 2005-06-16 at 07:46 -0700, Todd Landfried wrote:
> Yes, it is 7.2. Why? because an older version of our software runs on
> RH7.3 and that was the latest supported release of Postgresql for
> RH7.3 (that we can find). We're currently ported to 8, but we still
> have a large installed base with the other version.
>
>
> On Jun 15, 2005, at 7:18 AM, Tom Lane wrote:
>
> > Dennis Bjorklund <db@zigo.dhs.org> writes:
> >
> >> On Wed, 15 Jun 2005, Todd Landfried wrote:
> >>
> >>> NOTICE: shared_buffers is 256
> >>>
> >
> >
> >> This looks like it's way too low. Try something like 2048.
> >>
> >
> > It also is evidently PG 7.2 or before; SHOW's output hasn't looked
> > like
> > that in years. Try a more recent release --- there's usually
> > nontrivial
> > performance improvements in each major release.
> >
> > regards, tom lane
> >
> > ---------------------------(end of
> > broadcast)---------------------------
> > TIP 2: you can get off all lists at once with the unregister command
> > (send "unregister YourEmailAddressHere" to
> > majordomo@postgresql.org)
> >
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mark.lewis@mir3.com, tlandfried@viatornetworks.com
Subject: Re: Needed: Simplified guide to optimal memory
In-Reply-To: <1118941260.698.5.camel@archimedes.mirlogic.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox