| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Mike Blackwell <mike(dot)blackwell(at)rrd(dot)com>, PgHacker <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: RULE regression test fragility? |
| Date: | 2013-10-25 13:50:57 |
| Message-ID: | 20131025135057.GF6832@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund wrote:
> On 2013-10-24 09:22:52 -0400, Tom Lane wrote:
> > Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> > > FWIW, I've repeatedly now thought that it'd make maintaining/updating
> > > patches easier if we switched that query into unaligned tuple only (\a
> > > \t) mode. That would remove the frequent conflicts on the row count and
> > > widespread changes due to changed alignment.
> > > Alternatively we could just wrap the query in \copy ... CSV.
> >
> > Hm ... yeah, it would be a good thing if changes in one view didn't so
> > frequently have ripple effects to the whole output. Not sure which
> > format is best for that though.
>
> Something like the attached maybe?
+1 (but what are those silly parens in pg_seclabels definition?),
except:
> +-- disable fancy output again
> +\a\t
Should be "enable".
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-10-25 14:11:22 | Re: RULE regression test fragility? |
| Previous Message | Tom Lane | 2013-10-25 13:41:43 | Re: Example query causing param_info to be set in plain rel path |