| From: | "Igor Neyman" <ineyman(at)perceptron(dot)com> |
|---|---|
| To: | "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Jay Levitt" <jay(dot)levitt(at)gmail(dot)com>, <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Guide to PG's capabilities for inlining, predicate hoisting, flattening, etc? |
| Date: | 2011-11-02 20:22:36 |
| Message-ID: | F4C27E77F7A33E4CA98C19A9DC6722A2084DFFF7@EXCHANGE.corp.perceptron.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> -----Original Message-----
> From: Robert Haas [mailto:robertmhaas(at)gmail(dot)com]
> Sent: Wednesday, November 02, 2011 11:13 AM
> To: Tom Lane
> Cc: Jay Levitt; pgsql-performance(at)postgresql(dot)org
> Subject: Re: Guide to PG's capabilities for inlining, predicate
> hoisting, flattening, etc?
> .......
> .......
> Perhaps we could let people say
> something like WITH x AS FENCE (...) when they want the fencing
> behavior, and otherwise assume they don't (but give it to them anyway
> if there's a data-modifying operation in there).
>
> ....
> ....
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
Hints.... here we come :)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yeb Havinga | 2011-11-02 20:45:05 | Re: Intel 710 pgbench write latencies |
| Previous Message | CS DBA | 2011-11-02 20:21:18 | Poor performance on a simple join |