Skip to content

Tags: mhagander/postgres

Tags

REL9_0_1

Toggle REL9_0_1's commit message
Fix back-branch breakage from ill-advised last-minute commit.

REL8_4_5

Toggle REL8_4_5's commit message
Tag 8.4.5

REL8_3_12

Toggle REL8_3_12's commit message
Tag 8.3.12

REL8_2_18

Toggle REL8_2_18's commit message
Tag 8.2.18

REL8_1_22

Toggle REL8_1_22's commit message
Tag 8.1.22

REL8_0_26

Toggle REL8_0_26's commit message
Tag 8.0.26

REL7_4_30

Toggle REL7_4_30's commit message
Tag 7.4.30

REL9_0_0

Toggle REL9_0_0's commit message

tag v9.0.0 ... the big day approaches

REL9_1_ALPHA1

Toggle REL9_1_ALPHA1's commit message
Install a data-type-based solution for protecting pg_get_expr().

Since the code underlying pg_get_expr() is not secure against malformed
input, and can't practically be made so, we need to prevent miscreants
from feeding arbitrary data to it.  We can do this securely by declaring
pg_get_expr() to take a new datatype "pg_node_tree" and declaring the
system catalog columns that hold nodeToString output to be of that type.
There is no way at SQL level to create a non-null value of type pg_node_tree.
Since the backend-internal operations that fill those catalog columns
operate below the SQL level, they are oblivious to the datatype relabeling
and don't need any changes.

REL9_0_RC1

Toggle REL9_0_RC1's commit message

tag rc1 ... final stretch ...