[postgis-users] PostgreSQL 8.3.8 and 8.4.1 out

[P Kishor]

On Sun, Sep 13, 2009 at 7:40 PM, Paragon Corporation <lr at pcorp.us> wrote:
> If you are running 8.3.5+
> Just replace the binaries for PostgreSQL (so if you compiled yourself, I
> guess that would be a recompile for you and install).   No change at all
> needed for the PostGIS part of it.
>
> For Linux -- if you are using the yum repository its just Yum upgrade
> For windows -- just download the PostgreSQL 8.3.8 and install ontop of your
> PostgreSQL 8.3.x (if you are running  8.3.5+) - again nothing to do for
> PostGIS
>
> Hope that helps,


Right. Actually, I am running the one OS not mentioned above... Mac OS
X. However, since I compiled everything meself, I guess I just
recompile and install PostGres. However, since my data lives at
/usr/local/pgsql/data, I am hoping that won't get disturbed by the Pg
install, or will it?

> Regina
>
> -----Original Message-----
> From: postgis-users-bounces at postgis.refractions.net
> [mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of P Kishor
> Sent: Sunday, September 13, 2009 6:24 PM
> To: PostGIS Users Discussion
> Subject: Re: [postgis-users] PostgreSQL 8.3.8 and 8.4.1 out
>
> On Sun, Sep 13, 2009 at 12:31 AM, Paragon Corporation <lr at pcorp.us> wrote:
>> Just in case some people don't know.
>>
>> PostgreSQL 8.3.8 and 8.4.1 came out last week and while they are
>> mostly security bug fixes, they do include some speed enhancements.
>>
>
> I have PostGIS 1.4/PostGres 8.4. What is the recommended way of upgrading
> this combo? Do I have to recompile PostGres and then PostGIS again? Do I
> have to rebuild my databases? Is there a tutorial/knowledgebase article on
> the various upgrade paths possible?
>
>
>> For 8.4.1 -- "improve performance when processing toasted values in
>> index scans"
>>
>> Which fixes the below bug.
>>
>> http://postgis.refractions.net/pipermail/postgis-devel/2009-August/006
>> 659.ht
>> ml
>> (though I guess it wasn't backported to 8.3 since I don't see it
>> listed in
>> 8.3.8 release notes)
>>
>> http://www.postgresql.org/docs/8.4/static/release-8-4-1.html
>>
>> For both 8.3.8, 8.4.1 -- has for "Fix Windows shared-memory allocation "
>> This bug led to the often-reported "could not reattach to shared memory"
>>
>> http://www.postgresql.org/docs/8.3/static/release-8-3-8.html
>>
>> Hope that helps,
>> Regina
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> postgis-users mailing list
>> postgis-users at postgis.refractions.net
>> http://postgis.refractions.net/mailman/listinfo/postgis-users
>>
>
>
>
> --
> Puneet Kishor http://www.punkish.org
> Carbon Model http://carbonmodel.org
> Charter Member, Open Source Geospatial Foundation http://www.osgeo.org
> Science Commons Fellow, http://sciencecommons.org/about/whoweare/kishor
> Nelson Institute, UW-Madison http://www.nelson.wisc.edu
> -----------------------------------------------------------------------
> Assertions are politics; backing up assertions with evidence is science
> =======================================================================
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>