On 2013-10-25 10:50:57 -0300, Alvaro Herrera wrote:
> Andres Freund wrote:
> > On 2013-10-24 09:22:52 -0400, Tom Lane wrote:
> > > Andres Freund <andres@2ndquadrant.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?),
That's because it contain several UNION ALLs and ruleutils makes sure
the order is correct.
> except:
>
> > +-- disable fancy output again
> > +\a\t
>
> Should be "enable".
Hrmpf. Fixed.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services