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
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
|
2010-xx-xx - PlProxy 2.1 - ""
= Features =
* SPLIT: New SPLIT statement to convert incoming array arguments
into smaller per-partition arrays:
http://plproxy.projects.postgresql.org/doc/syntax.html#_split
(Martin Pihlak)
* SQL/MED: Cluster can be defined with SQL/MED facilities,
instead of old-style plproxy.* functions.
http://plproxy.projects.postgresql.org/doc/config.html
(Martin Pihlak)
= Minor fixes/features =
* Allow to customize location to pg_config via PG_CONFIG make variable.
(David E. Wheeler)
* Remote errors and notices are now passed upwards with all details.
Previously only error message pas passed and notices were ignored.
* Compatible with Postgres 9.0.
* Compatible with flex 2.5.35+ - it now properly defines it's
own functions, so PL/Proxy does not need to do it. Otherwise
compilation will fail if flex definitions are hacked (MacOS).
* Rework regests to make them work across 8.2..9.0 and decrease
chance of spurious failures. The encoding test still fails
if Postgres instance is not created with LANG=C.
* deb: per-version packaging: `make debXY` will create
`postgresql-plproxy-X.Y` package.
2009-10-28 - PlProxy 2.0.9 - "Five-Nines Guarantee For Not Bricking The Server"
= Features =
* More flexible CONNECT statement:
CONNECT func(..);
CONNECT argname;
CONNECT $argnum;
NB: giving untrusted users ability to specify full connect string creates
security hole. Eg it can used to read cleartext passwords from .pgpass/pg_service.
If such function cannot be avoided, it's access rights need to be restricted.
(Ian Sollars)
= Fixes =
* Avoid parsing "SELECT (" as function call. Otherwise following query
fails to parse: SELECT (0*0);
(Peter Eisentraut)
* Make scanner accept dot as standalone symbol. Otherwise following query
fails to parse: SELECT (ret_numtuple(1)).num, (ret_numtuple(1)).name;
(Peter Eisentraut)
* Argument type name length over 32 could cause buffer overflow.
(Ian Sollars)
* Fix crash with incoming NULL value in function containing SELECT
with different argument order. Due to thinko, NULL check was done
with query arg index, instead of function arg index.
(João Matos)
* geterrcode(): Switch memory context to work around Assert() in CopyErrorData().
2009-01-16 - PlProxy 2.0.8 - "Simple Multi-Tentacle Arhitecture"
= Features =
* If query is canceled, send cancel request to remote db too.
(Ye Wenbin)
* Allow direct argument references in RUN ON statement.
Now this works: RUN ON $1; RUN ON arg;
* Add FAQ to docs which answers few common questions.
= Fixes =
* Clear ->tuning bit on connection close.
If 'SET client_encoding' fails, the bit can stay set,
thus creating always-failing connection slot.
Reported and analyzed by Jonah Harris.
2008-09-29 - PlProxy 2.0.7 - "The Ninja of Shadow"
= Fixes =
* Make sure client_encoding on remote server encoding is set to
local server encoding. Currently plproxy set it to local
client_encoding, which is wrong as all data is immediately converted
to server_encoding by Postgres. The problem went mostly undetected
because of plproxy use of binary I/O which bypasses encoding
conversions.
(Hiroshi Saito)
So if you pass non-ascii data around and your client, proxy server
and target server may have different encodings, you may want to
re-check your data.
* Disable binary i/o completely. Currently the decision is done
too early, before remote connection is established. Currently
the fix was to use only "safe" types for binary I/O, but now
that text types are also unsafe, it's pointless. Instead
type handling should be rewritten to allow lazy decision-making.
* Fix crash with unnamed function input arguments.
* Fix compilation with 8.2 on Win32 by providing PGDLLIMPORT if unset.
(Hiroshi Saito)
* Accept >128 chars as part of identifier names.
* New regtest to detect encoding problems.
* Use pg_strcasecmp instead of strcasecmp to be consistent with
Postgres code.
* deb: Survive empty FLEX/BISON defs from PGXS.
Accept also postgresql-server-dev-8.3 as build dep.
2008-09-05 - PlProxy 2.0.6 - "Agile Voodoo"
= Features =
* Support functions that return plain RECORD without
OUT parameters. Such functions need result type
specified on each call with AS clause and the
types need to be sent to remote database also.
(Lei Yonghua)
This makes possible to use PL/Proxy for dynamic queries:
CREATE FUNCTION run_query(sql text) RETURNS RECORD ..
SELECT * FROM run_query('select a,b from ..') AS (a int, b text);
* Accept int2/int8 values from hash function,
in addition to int4.
= Fixes =
* Replace bitfields with bool to conform better
with Postgres coding style.
* Don't use alloca() in parser.
* Make scanner more robust to allocation errors
by doing total reset before parsing.
* Require exactly one row from remote query for
non-SETOF functions.
* Docs: tag all functions with embedded SELECT with SETOF.
* Make it compile on win32 (Hiroshi Saito)
* Make regtest tolerant to random() implementation differneces
between different OSes.
2008-06-06 - PlProxy 2.0.5 - "Universal Shredder"
* Fix crash if a function with "CLUSTER 'name';"
is parsed after function with "CLUSTER func();".
A palloc()ed pointer was not reset.
* RUN ON is now optional, defaulting to RUN ON ANY;
Should make creating simple RPC and load-balancing
functions easier easier.
* Make compat poll() function behave more like actual poll().
2008-01-04 - PlProxy 2.0.4 - "Vampire-proof"
* Fix crash due to bad error reporting when remote db
closes socket unexpectedly.
* Use pg_strcasecmp to compare encodings.
* Log encoding values if it fails to apply.
* Replace select(2) with poll(2) to allow large fd values.
Old select(2) usage could cause problems when plproxy
was installed on database with lot of tables/indexes,
where Postgres itself could have had lot of files open.
* Disable binary I/O for timestamp(tz) and date/time types,
to avoid problems when local and remote Postgres have
different setting for integer_datetimes.
2007-12-10 - PlProxy 2.0.3 - "Faster Than A Fresh Zombie"
= Features =
* Explicitly specify result column names and types in query.
Lets say there is function somefunc(out id int4, out data text).
Previously pl/proxy issued following query:
SELECT * FROM somefunc()
And later tried to work out which column goes where. Now it issues:
SELECT id::int4, data::text FROM somefunc()
For functions without named return paramenters, eg. just "RETURNS text":
SELECT r::text FROM anotherfunc() r
This gives better type safety when using binary I/O, allows signatures
differ in deterministic ways and creates safe upgrade path for signatures.
Only downside is that existing functions with wildly different signatures
stop working, but as they work on pure luck anyway, I'm not worried.
* Quote function and result column names properly.
* Set client_encoding on remote database to be equal to local one.
* Tutorial by Steve Singer.
= Fixes =
* Support 8.3 (handle short varlena header)
* Support old flex (2.5.4) Previously flex >= 2.5.33 was required.
* Fix 'make deb', include actual debian/changelog.
* Remove config paramenter 'statement_timeout'.
It was ignored previously and it cannot be made work in live env
when working thru pgbouncer, so its better to drop it completely.
The setting can be always set via normal ways.
2007-04-16 - PlProxy 2.0.2 - "No news is good news?"
* Include plproxy.sql.in in tgz.
* Clean add_connection() function by using StringInfo instead
open-coded string shuffling.
|
