Re: Replacing the pg_get_expr security hack with a datatype solution

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Replacing the pg_get_expr security hack with a datatype solution
Date: 2010-09-02 22:21:09
Message-ID: 15512.1283466069@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> On lr, 2010-08-21 at 15:30 -0400, Tom Lane wrote:
>> The only thing that seems like it might need discussion is the name
>> to give the datatype. My first instinct was pg_expr or pg_expression,
>> but there are some cases where this doesn't exactly fit. In
>> particular,
>> pg_rewrite.ev_action contains a whole Query, in fact a list of them.

> Perhaps pg_node then.

pg_node sounds like there's just one. Maybe pg_node_tree?

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message John Adams 2010-09-02 22:25:45 returning multiple result sets from a stored procedure
Previous Message Tom Lane 2010-09-02 21:31:12 Cost estimates for parameterized paths