1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
|
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>E.79.Release 1.01</title>
<link rel="stylesheet" href="stylesheet.css" type="text/css">
<link rev="made" href="pgsql-docs@postgresql.org">
<meta name="generator" content="DocBook XSL Stylesheets V1.70.0">
<link rel="start" href="index.html" title="PostgreSQL 8.1.4 Documentation">
<link rel="up" href="release.html" title="AppendixE.Release Notes">
<link rel="prev" href="release-1-02.html" title="E.78.Release 1.02">
<link rel="next" href="release-1-0.html" title="E.80.Release 1.0">
<link rel="copyright" href="ln-legalnotice.html" title="Legal Notice">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="sect1" lang="en">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="release-1-01"></a>E.79.Release 1.01</h2></div></div></div>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Release date</h3>
<p>1996-02-23</p>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id897816"></a>E.79.1.Migration from version 1.0 to version 1.01</h3></div></div></div>
<p>The following notes are for the benefit of users who want to migrate
databases from <span class="productname">Postgres95</span> 1.0 to <span class="productname">Postgres95</span> 1.01. </p>
<p>If you are starting afresh with <span class="productname">Postgres95</span> 1.01 and do not need
to migrate old databases, you do not need to read any further.</p>
<p>In order to <span class="productname">Postgres95</span> version 1.01 with databases created with
<span class="productname">Postgres95</span> version 1.0, the following steps are required: </p>
<div class="procedure"><ol type="1">
<li><p>Set the definition of <code class="symbol">NAMEDATALEN</code> in <code class="filename">src/Makefile.global</code> to 16
and <code class="symbol">OIDNAMELEN</code> to 20.</p></li>
<li>
<p>Decide whether you want to use Host based authentication. </p>
<ol type="a">
<li><p>If you do, you must create a file name <code class="literal">pg_hba</code> in your top-level data
directory (typically the value of your <code class="envar">$PGDATA</code>). <code class="filename">src/libpq/pg_hba</code>
shows an example syntax.</p></li>
<li>
<p>If you do not want host-based authentication, you can comment out
the line
</p>
<pre class="programlisting"> HBA = 1</pre>
<p>
in <code class="filename">src/Makefile.global</code></p>
<p> Note that host-based authentication is turned on by default, and if
you do not take steps A or B above, the out-of-the-box 1.01 will
not allow you to connect to 1.0 databases.</p>
</li>
</ol>
</li>
<li><p>Compile and install 1.01, but DO NOT do the <code class="command">initdb</code> step.</p></li>
<li><p>Before doing anything else, terminate your 1.0 postmaster, and
backup your existing <code class="envar">$PGDATA</code> directory. </p></li>
<li><p>Set your <code class="envar">PGDATA</code> environment variable to your 1.0 databases, but set up
path up so that 1.01 binaries are being used.</p></li>
<li><p>Modify the file <code class="filename"><code class="envar">$PGDATA</code>/PG_VERSION</code> from 5.0 to 5.1</p></li>
<li><p>Start up a new 1.01 postmaster</p></li>
<li>
<p>Add the new built-in functions and operators of 1.01 to 1.0
databases. This is done by running the new 1.01 server against
your own 1.0 database and applying the queries attached and saving
in the file 1.0_to_1.01.sql. This can be done easily through <code class="command">psql</code>.
If your 1.0 database is name <code class="literal">testdb</code>:
</p>
<pre class="programlisting"> % psql testdb -f 1.0_to_1.01.sql</pre>
<p>
and then execute the following commands (cut and paste from here):
</p>
<pre class="programlisting">-- add builtin functions that are new to 1.01
create function int4eqoid (int4, oid) returns bool as 'foo'
language 'internal';
create function oideqint4 (oid, int4) returns bool as 'foo'
language 'internal';
create function char2icregexeq (char2, text) returns bool as 'foo'
language 'internal';
create function char2icregexne (char2, text) returns bool as 'foo'
language 'internal';
create function char4icregexeq (char4, text) returns bool as 'foo'
language 'internal';
create function char4icregexne (char4, text) returns bool as 'foo'
language 'internal';
create function char8icregexeq (char8, text) returns bool as 'foo'
language 'internal';
create function char8icregexne (char8, text) returns bool as 'foo'
language 'internal';
create function char16icregexeq (char16, text) returns bool as 'foo'
language 'internal';
create function char16icregexne (char16, text) returns bool as 'foo'
language 'internal';
create function texticregexeq (text, text) returns bool as 'foo'
language 'internal';
create function texticregexne (text, text) returns bool as 'foo'
language 'internal';
-- add builtin functions that are new to 1.01
create operator = (leftarg = int4, rightarg = oid, procedure = int4eqoid);
create operator = (leftarg = oid, rightarg = int4, procedure = oideqint4);
create operator ~* (leftarg = char2, rightarg = text, procedure = char2icregexeq);
create operator !~* (leftarg = char2, rightarg = text, procedure = char2icregexne);
create operator ~* (leftarg = char4, rightarg = text, procedure = char4icregexeq);
create operator !~* (leftarg = char4, rightarg = text, procedure = char4icregexne);
create operator ~* (leftarg = char8, rightarg = text, procedure = char8icregexeq);
create operator !~* (leftarg = char8, rightarg = text, procedure = char8icregexne);
create operator ~* (leftarg = char16, rightarg = text, procedure = char16icregexeq);
create operator !~* (leftarg = char16, rightarg = text, procedure = char16icregexne);
create operator ~* (leftarg = text, rightarg = text, procedure = texticregexeq);
create operator !~* (leftarg = text, rightarg = text, procedure = texticregexne);</pre>
</li>
</ol></div>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id898087"></a>E.79.2.Changes</h3></div></div></div>
<pre class="programlisting">Incompatibilities:
* 1.01 is backwards compatible with 1.0 database provided the user
follow the steps outlined in the MIGRATION_from_1.0_to_1.01 file.
If those steps are not taken, 1.01 is not compatible with 1.0 database.
Enhancements:
* added PQdisplayTuples() to libpq and changed monitor and psql to use it
* added NeXT port (requires SysVIPC implementation)
* added CAST .. AS ... syntax
* added ASC and DESC key words
* added 'internal' as a possible language for CREATE FUNCTION
internal functions are C functions which have been statically linked
into the postgres backend.
* a new type "name" has been added for system identifiers (table names,
attribute names, etc.) This replaces the old char16 type. The
of name is set by the NAMEDATALEN #define in src/Makefile.global
* a readable reference manual that describes the query language.
* added host-based access control. A configuration file ($PGDATA/pg_hba)
is used to hold the configuration data. If host-based access control
is not desired, comment out HBA=1 in src/Makefile.global.
* changed regex handling to be uniform use of Henry Spencer's regex code
regardless of platform. The regex code is included in the distribution
* added functions and operators for case-insensitive regular expressions.
The operators are ~* and !~*.
* pg_dump uses COPY instead of SELECT loop for better performance
Bug fixes:
* fixed an optimizer bug that was causing core dumps when
functions calls were used in comparisons in the WHERE clause
* changed all uses of getuid to geteuid so that effective uids are used
* psql now returns non-zero status on errors when using -c
* applied public patches 1-14</pre>
</div>
</div></body>
</html>
|
