On Fri, Feb 11, 2011 at 10:52 AM, Stephen Frost <sfr...@snowman.net> wrote: > * Robert Haas (robertmh...@gmail.com) wrote: >> On Fri, Feb 11, 2011 at 10:34 AM, Kevin Grittner >> > Should we abbreviate something there? max_pred_locks_per_tran, >> > maybe? >> >> If we're going to abbreviate transaction, I'd vote for txn over tran, >> but I think Stephen's point that this is already a lost cause may have >> some validity. Not sure what other people think. > > There's lots of other GUCs with "transaction" spelled out in them.. :/ > > Another option, which I don't like, would be to use 'default' by > 'default', and build the list on the fly every time if that's what it > is.. That would give no insight into what the list of fields is for > someone though, they'd have to go back to the documentation to figure > it out, and that sucks..
Yeah. The root cause of this problem is that the way psql handles tabular output with a few very wide rows stinks. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
