No subject
Tue Oct 7 10:08:30 PDT 2008
massaging if you know what you are doing) since aggregate functions don't
carry over.
Hope that answers your question,
Regina
_____
From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of Ben
Madin
Sent: Sunday, September 13, 2009 6:23 PM
To: PostGIS Users Discussion
Subject: [postgis-users] HARD or SOFT upgrade - documentation questions.
And since I'm following the manual, two more questions:
1. Does hard / soft upgrades refer to changes in PostGIS, or changes in
PostgreSQL, or both? Having soft upgraded PostGIS from 1.3.6 to 1.4.0 I
wonder if it is more relevant to the PostgreSQL version number.
2. In the manual, it has the following line :
2.7.2. Hard upgrade
By HARD UPGRADE we intend full dump/reload of postgis-enabled databases. You
need an HARD UPGRADE when postgis objects' internal storage changes or when
SOFT UPGRADE is not possible. The Release
<http://postgis.refractions.net/documentation/manual-1.4/release_notes.html>
Notes appendix reports for each version whether you need a dump/reload (HARD
UPGRADE) to upgrade.
but in the Release Notes appendix I can't find anywhere any guidance on
whether I need a hard or soft upgrade.
cheers
Ben
--
Ben Madin
REMOTE INFORMATION
t : +61 8 9192 5455
f : +61 8 9192 5535
m : 0448 887 220
Broome WA 6725
ben at remoteinformation.com.au
Out here, it pays to know...
------=_NextPart_000_0010_01CA34B5.4017FFC0
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6001.18294" name=3DGENERATOR></HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space">
<DIV dir=3Dltr align=3Dleft><SPAN class=3D308545500-14092009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Ben,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D308545500-14092009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D308545500-14092009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Sorry about that. The upgrade =
section of the=20
docs does need sufficient revamp. But been putting it of since =
we've been=20
working on revamping this process.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D308545500-14092009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D308545500-14092009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>The short answer -- Hard upgrade really doesn't =
have=20
anything to do with PostgreSQL version upgrade. AS long as you =
have the=20
same version of PostGIS in your new install as you did in your old=20
install. Hard upgrade doesn't come into play.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D308545500-14092009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D308545500-14092009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>In the past -- it was kind of iffy when you =
needed to do a=20
Hard upgrade vs. a soft upgrade.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D308545500-14092009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D308545500-14092009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Moving forward -- a hard upgrade is only needed =
if you are=20
moving from major to major version (e.g. from a 1.3 -->=20
2.0)</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D308545500-14092009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Soft upgrade -- 1.3 ->1.4 , =
1.3->1.5=20
etc.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D308545500-14092009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D308545500-14092009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>From 1.2 its kind of iffy -- you really should =
do a hard=20
upgrade (or manual massaging if you know what you are doing) since =
aggregate=20
functions don't carry over.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D308545500-14092009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D308545500-14092009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hope that answers your =
question,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D308545500-14092009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Regina</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B>=20
postgis-users-bounces at postgis.refractions.net=20
[mailto:postgis-users-bounces at postgis.refractions.net] <B>On Behalf Of =
</B>Ben=20
Madin<BR><B>Sent:</B> Sunday, September 13, 2009 6:23 PM<BR><B>To:</B> =
PostGIS=20
Users Discussion<BR><B>Subject:</B> [postgis-users] HARD or SOFT upgrade =
-=20
documentation questions.<BR></FONT><BR></DIV>
<DIV></DIV>And since I'm following the manual, two more questions:
<DIV><BR></DIV>
<DIV>1. Does hard / soft upgrades refer to changes in PostGIS, or =
changes in=20
PostgreSQL, or both? Having soft upgraded PostGIS from 1.3.6 to 1.4.0 I =
wonder=20
if it is more relevant to the PostgreSQL version number.</DIV>
<DIV><BR></DIV>
<DIV>2. In the manual, it has the following line :</DIV>
<DIV><BR></DIV>
<DIV><SPAN class=3DApple-style-span=20
style=3D"FONT-SIZE: 14px; COLOR: rgb(46,46,46); FONT-FAMILY: 'Lucida =
Grande', Verdana, Geneva, Arial, Helvetica, sans-serif">
<DIV class=3Dtitlepage>
<DIV>
<DIV>
<H3 class=3Dtitle=20
style=3D"FONT-SIZE: 16px; MARGIN-BOTTOM: 16px; COLOR: rgb(33,55,128); =
LINE-HEIGHT: 18px">2.7.2. Hard=20
upgrade</H3></DIV></DIV></DIV>
<P style=3D"FONT-SIZE: 10pt">By HARD UPGRADE we intend full dump/reload =
of=20
postgis-enabled databases. You need an HARD UPGRADE when postgis =
objects'=20
internal storage changes or when SOFT UPGRADE is not possible. =
The <A=20
title=3DAppendix A. Appendix=20
style=3D"COLOR: rgb(65,138,205); TEXT-DECORATION: none"=20
href=3D"http://postgis.refractions.net/documentation/manual-1.4/release_n=
otes.html">Release=20
Notes</A> appendix reports for each version whether you need a =
dump/reload=20
(HARD UPGRADE) to upgrade.</P>
<DIV><FONT class=3DApple-style-span size=3D3><SPAN =
class=3DApple-style-span=20
style=3D"FONT-SIZE: 13px"><BR></SPAN></FONT></DIV></SPAN></DIV>
<DIV>but in the Release Notes appendix I can't find anywhere any =
guidance on=20
whether I need a hard or soft upgrade. </DIV>
<DIV><BR>
<DIV>cheers</DIV>
<DIV><BR></DIV>
<DIV>Ben</DIV>
<DIV><BR></DIV>
<DIV><BR>
<DIV><SPAN class=3DApple-style-span=20
style=3D"WORD-SPACING: 0px; FONT: medium Helvetica; TEXT-TRANSFORM: =
none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px">
<DIV><BR class=3DApple-interchange-newline>-- </DIV>
<DIV><BR>Ben Madin<BR>REMOTE INFORMATION<BR><BR>t : +61 8 9192 5455<BR>f =
: +61 8=20
9192 5535<BR>m : 0448 887 220<BR>Broome WA=20
6725<BR><BR><A=20
href=3D"mailto:ben at remoteinformation.com.au">ben at remoteinformation.com.au=
</A><BR><BR><BR><BR><SPAN=20
class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN><SPAN =
class=3DApple-tab-span=20
style=3D"WHITE-SPACE: pre"></SPAN><SPAN class=3DApple-tab-span=20
style=3D"WHITE-SPACE: pre"></SPAN><SPAN class=3DApple-tab-span=20
style=3D"WHITE-SPACE: pre"></SPAN><SPAN class=3DApple-tab-span=20
style=3D"WHITE-SPACE: pre"></SPAN><SPAN class=3DApple-tab-span=20
style=3D"WHITE-SPACE: pre"></SPAN><SPAN class=3DApple-tab-span=20
style=3D"WHITE-SPACE: pre"></SPAN>Out here, it pays to=20
know...<BR><BR></DIV></SPAN></DIV><BR></DIV></DIV></BODY></HTML>
------=_NextPart_000_0010_01CA34B5.4017FFC0--