Re: [HACKERS] Spaces in psql output (Was: FW: PGBuildfarm member snake Branch HEAD Status changed)

2006-02-10 Thread Tom Lane
Martijn van Oosterhout writes: > The extra spaces is an interesting side-effect. In the past it would > only have worked for the last column anyway, right? Of course. > Anyway, it is a fixable issue and I'd consider doing it if people think > it's worth it. I think it would be a good idea to ex

Re: [HACKERS] Spaces in psql output (Was: FW: PGBuildfarm member snake Branch HEAD Status changed)

2006-02-10 Thread Michael Paesold
Martijn van Oosterhout wrote: On Fri, Feb 10, 2006 at 08:06:53PM +0100, Michael Paesold wrote: > A side affect of this newline patch is that all fields are now filled > with > white space up to the displayed column width, even for the last (or only > column). My intention was to only change f

Re: [HACKERS] Spaces in psql output (Was: FW: PGBuildfarm member snake Branch HEAD Status changed)

2006-02-10 Thread Martijn van Oosterhout
On Fri, Feb 10, 2006 at 08:06:53PM +0100, Michael Paesold wrote: > A side affect of this newline patch is that all fields are now filled with > white space up to the displayed column width, even for the last (or only > column). I guess this is somehow required for consistent display. > Otherwise

[HACKERS] Spaces in psql output (Was: FW: PGBuildfarm member snake Branch HEAD Status changed)

2006-02-10 Thread Michael Paesold
Bruce Momjian wrote: The failure, I think, it because of the newline patch we got for psql yesterday. I am seeking a diff from pgcrypto to fix it. My openssl is too old. A side affect of this newline patch is that all fields are now filled with white space up to the displayed column width