| From: | Grzegorz Jaskiewicz <gj(at)pointblue(dot)com(dot)pl> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | David Fetter <david(at)fetter(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christian Schröder <cs(at)deriva(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] Performance of full outer join in 8.3 |
| Date: | 2009-04-16 18:45:47 |
| Message-ID: | 9B0D1547-B358-426B-A6DC-4A3D2E97F236@pointblue.com.pl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On 16 Apr 2009, at 19:41, Merlin Moncure wrote:
>
> Is that because of how the output is formatted though, or because the
> concepts are difficult to express? (I agree though, json is better
> especially for structures that are possibly highly nested).
What I mean is that what postgresql displays currently as
explain(analyze[verbose]) is clear and understandable.
Also, it is getting better and better from version to version. So I
don't personally agree, that it is unreadable - and I am up for (and I
am sure many users like me are) JSON, or XML output.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bill Moran | 2009-04-16 19:40:12 | Looking for advice on database encryption |
| Previous Message | Merlin Moncure | 2009-04-16 18:41:15 | Re: [GENERAL] Performance of full outer join in 8.3 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2009-04-16 19:04:37 | Re: [rfc] unicode escapes for extended strings |
| Previous Message | Sam Mason | 2009-04-16 18:43:09 | Re: [rfc] unicode escapes for extended strings |