| From: | Antonin Houska <ah(at)cybertec(dot)at> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: from_collapse_limit considerations |
| Date: | 2014-10-22 14:57:42 |
| Message-ID: | 26340.1413989862@linux-at0a.site |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
[ I think I responded earlier but don't see my mail in the archive... ]
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Antonin Houska <ah(at)cybertec(dot)at> writes:
> > I noticed that - unlike join_collapse_limit - the from_collapse_limit does not
> > enforce maximum length of the top-level list. Shouldn't it do?
>
> How would it do that? You want it to fail outright if there are more than
> N tables? That seems unhelpful.
Sure, truncation of the FROM list would be crazy, and that's not what I tried to propose.
--
Antonin Houska
Cybertec Schönig & Schönig GmbH
Gröhrmühlgasse 26
A-2700 Wiener Neustadt
Web: http://www.postgresql-support.de, http://www.cybertec.at
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ali Akbar | 2014-10-22 14:58:10 | Re: Function array_agg(array) |
| Previous Message | Andres Freund | 2014-10-22 14:34:22 | Re: Wait free LW_SHARED acquisition - v0.2 |