postgresql/src/bin
Stephen Frost 82962838d4 Handle border = 3 in expanded mode
In psql, expanded mode was not being displayed correctly when using
the normal ascii or unicode linestyles and border set to '3'.  Now,
per the documentation, border '3' is really only sensible for HTML
and LaTeX formats, however, that's no excuse for ascii/unicode to
break in that case, and provisions had been made for psql to cleanly
handle this case (and it did, in non-expanded mode).

This was broken when ascii/unicode was initially added a good five
years ago because print_aligned_vertical_line wasn't passed in the
border setting being used by print_aligned_vertical but instead was
given the whole printTableContent.  There really isn't a good reason
for vertical_line to have the entire printTableContent structure, so
just pass in the printTextFormat and border setting (similar to how
this is handled in horizontal_line).

Pointed out by Pavel Stehule, fix by me.

Back-patch to all currently-supported versions.
2014-09-12 11:11:53 -04:00
..
initdb Small message fixes 2014-08-09 00:07:00 -04:00
pg_basebackup Add header comments to receivelog.h and streamutil.h. 2014-08-27 19:31:48 +09:00
pg_config Translation updates 2014-07-21 01:08:04 -04:00
pg_controldata Fix TAP installcheck tests when current directory name contains spaces 2014-07-23 22:06:56 -04:00
pg_ctl Assorted message improvements 2014-08-29 00:26:17 -04:00
pg_dump Report timezone offset in pg_dump/pg_dumpall 2014-09-05 19:22:31 -04:00
pg_resetxlog Small message fixes 2014-08-09 00:07:00 -04:00
pgevent Properly use DEFAULT_EVENT_SOURCE in pgevent.c 2014-07-21 12:24:00 +02:00
psql Handle border = 3 in expanded mode 2014-09-12 11:11:53 -04:00
scripts Fix vacuumdb --analyze-in-stages --all order 2014-09-11 21:40:46 -04:00
Makefile Update copyright for 2014 2014-01-07 16:05:30 -05:00