On Wed, Jun 11, 2014 at 10:16 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Noah Misch <n...@leadboat.com> writes: >> Based on the commit message and procedural history, I thought commit 6513633 >> was changing behavior solely for the combination of "\pset expanded" and >> "\pset format wrapped". Peter's and my test cases show that it also changed >> behavior for "\pset expanded" alone. That's a bug, unless someone sees to >> argue that the new "\pset expanded" behavior is a desirable improvement in >> spite of its origin as an accident. Altering an entrenched psql output >> format >> is a big deal. > > TBH I'm wondering if we shouldn't just revert that patch (and the > subsequent fix attempts). It was not a major feature and I'm thinking > we have better things to do right now than try to fix the multiple > logic holes it evidently has. The author's certainly welcome to try > again with a more carefully thought-through patch for 9.5.
So, it seems like we need to do something about this one way or another. Who's working on that? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers