| From: | Emmanuel Cecchet <manu(at)asterdata(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Emmanuel Cecchet <manu(at)asterdata(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Emmanuel Cecchet <Emmanuel(dot)Cecchet(at)asterdata(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: COPY enhancements |
| Date: | 2009-09-11 22:56:42 |
| Message-ID: | 4AAAD5AA.8080706@asterdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas wrote:
> http://developer.postgresql.org/pgdocs/postgres/sql-explain.html
>
Just out of curiosity, it looks like I could write something like:
EXPLAIN (ANALYZE TRUE, COSTS FALSE, VERBOSE TRUE, COSTS TRUE) statement
What is the expected behavior if someone puts multiple time the same
option with different values. The last value prevails?
I know that this example looks stupid but when you have a lot of options
it sometimes happen that you put twice an option with different values
(that happens with some JDBC driver options...).
manu
--
Emmanuel Cecchet
Aster Data Systems
Web: http://www.asterdata.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sam Mason | 2009-09-11 23:01:54 | Re: COALESCE and NULLIF semantics |
| Previous Message | Sam Mason | 2009-09-11 22:37:18 | Re: COALESCE and NULLIF semantics |