upgrade from 8.1.11 to 8.1.18

--_000_B0D7C0A3F35FE144A70312D086CBCA9B03A9A2D3DEExchMailbox 2u_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I need to upgrade postgresql from 8.1.11 to 8.1.18.
The documentation states to
REINDEX all GiST indexes and REINDEX hash indexes on interval columns after=
the upgrade.

I googled the two items only to find the same comment with no instructions =
on what they are or how to do it.
How can I check if I have any GiST indexes and hash indesxes on interval co=
lumns?
Is there a command to reindex all databases at once or must I do each indiv=
idually?

Thanks


Marc


--_000_B0D7C0A3F35FE144A70312D086CBCA9B03A9A2D3DEExchMailbox 2u_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Arial;
color:windowtext;}
[at] page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>I need to upgrade postgresql from 8.1.11 to 8.1.18.<o:p>=
</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>The documentation states to <o:p></o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>REINDEX all GiST indexes and REINDEX hash indexes on
interval columns after the upgrade.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>I googled the two items only to find the same comment wi=
th no
instructions on what they are or how to do it.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>How can I check if I have any GiST indexes and hash inde=
sxes
on interval columns?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Is there a command to reindex all databases at once or m=
ust
I do each individually?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'>Thanks<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span style=3D'font-size:1=
0.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span style=3D'fon=
t-size:10.0pt;
font-family:"Courier New"'>Marc </span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span style=3D=
'font-size:
12.0pt'><o:p> </o:p></span></font></p>

</div>

</body>

</html>

--_000_B0D7C0A3F35FE144A70312D086CBCA9B03A9A2D3DEExchMailbox 2u_--
Marc Fromm [ Mo, 12 Oktober 2009 22:15 ] [ ID #2018792 ]

Re: upgrade from 8.1.11 to 8.1.18

Indexes are created as B-tree type unless you explicitly call for
another type when creating the index. I get the impression that other
index types are not commonly used in most applications.

If you look at the index definition using, say, psql from the command
line, or a graphical tool like pgAdmin, look for the keyword 'btree'
after the index name but before the list of indexed columns. If all
your indexes have that, then you don't have any GiST or hash indexes.

In psql, type:

\d mytablename

to see the table definition, this will show the indexes on that table also.

If your database has a lot of tables/indexes such that it would take you
too long to inspect each one, then I don't know what you could do.
Maybe some of the more experienced folks on the list could suggest
something.

Lewis Kapell
Computer Operations
Seton Home Study School


Marc Fromm wrote:
> I need to upgrade postgresql from 8.1.11 to 8.1.18.
>
> The documentation states to
>
> REINDEX all GiST indexes and REINDEX hash indexes on interval columns
> after the upgrade.
>
>
>
> I googled the two items only to find the same comment with no
> instructions on what they are or how to do it.
>
> How can I check if I have any GiST indexes and hash indesxes on interval
> columns?
>
> Is there a command to reindex all databases at once or must I do each
> individually?
>
>
>
> Thanks
>
>
>
>
>
> Marc
>
>
>


--
Sent via pgsql-admin mailing list (pgsql-admin [at] postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Lewis Kapell [ Mo, 12 Oktober 2009 22:29 ] [ ID #2018793 ]
Datenbanken » gmane.comp.db.postgresql.admin » upgrade from 8.1.11 to 8.1.18

Vorheriges Thema: How to size a log file partition
Nächstes Thema: Application SID does not match Conductor SID