From: | "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Grzegorz Jaskiewicz" <gj(at)pointblue(dot)com(dot)pl>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: subquery in limit |
Date: | 2008-02-15 15:46:21 |
Message-ID: | 1A6E6D554222284AB25ABE3229A927627155C0@nrtexcus702.int.asurion.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com> writes:
> > I have no idea why you can't do a subquery in the limit
>
> It hasn't seemed worth putting any effort into --- AFAIR this is the
> first time anyone's even inquired about it. As you say, you can
always
> use a function.
>
> > And I'm sure someone will point out a more efficient way to write my
> > function without using pl/pgsql. :)
>
> Only that it doesn't seem a particularly bright idea to use SECURITY
> DEFINER for a function that will execute any arbitrary caller-provided
> SQL ...
>
LOL! I knew something in my code would trigger a response. :)
Jon
From | Date | Subject | |
---|---|---|---|
Next Message | Christian Robottom Reis | 2008-02-15 16:58:52 | CVS repository invalid revision |
Previous Message | Tom Lane | 2008-02-15 15:44:35 | Re: subquery in limit |