| From: | Douglas Doole <dougdoole(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Push limit to sort through a subquery |
| Date: | 2017-08-24 17:07:37 |
| Message-ID: | CADE5jYKAotQdSRp-7=fH-F3xcn2KotgvZmZ=XRYx-+ws1_XAuA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> I don't greatly like the way that the regression test case filters
> the output; it hides too much IMO. I'd be inclined to try to return
> the EXPLAIN output with as much detail preserved as possible. Maybe
> we could use regex substitution on lines of the output to get rid of
> stuff that won't be invariant.
>
My first thought was to do a regex over the explain output to mask the
troublesome value, but I couldn't figure out how to make it work and didn't
find an example (admittedly didn't spent a huge amount of time hunting
though). I'd love to see how to put it together.
Doug
- Salesforce
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-08-24 17:24:15 | Re: [PATCH] Push limit to sort through a subquery |
| Previous Message | Tom Lane | 2017-08-24 16:49:05 | Re: [PATCH] Push limit to sort through a subquery |