Re: Space Stalker in SQL Output - Mailing list pgsql-general

From Susan Hurst
Subject Re: Space Stalker in SQL Output
Date
Msg-id eccb720e4e62d02dccafdc12ad46ec6d@mail.brookhurstdata.net
Whole thread Raw
In response to Re: Space Stalker in SQL Output  (Jerry Sievers <gsievers19@comcast.net>)
Responses Re: Space Stalker in SQL Output  (Joe Conway <mail@joeconway.com>)
List pgsql-general
Wow!  The -A option worked perfectly!

Thanks for the syntax lesson Steve and Jerry!

Sue

---
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Susan E Hurst
Principal Consultant
Brookhurst Data LLC
Email: susan.hurst@brookhurstdata.com
Mobile: 314-486-3261

On 2018-06-27 14:38, Jerry Sievers wrote:
> Susan Hurst <susan.hurst@brookhurstdata.com> writes:
> 
>> Why would a psql statement insert a leading space into the output,
>> which is a single integer value?
>> 
>> The leading space caused my job call to fail elsewhere in the same
>> shell script as the psql call.  Here is the anonymized version of the
>> psql call to assign a value to a shell script variable:
>> 
>> IDz=`psql -d proddb -U produser -h 10.9.999.99 -p 99900 -t <
>> last_id.sql`
> 
> Get in the habit of including -A which gets rid of alignment padding in
> psql output.
> 
> As in...
> 
> shellvar=`psql -Atqc 'select froboz;'` $db
> 
> HTH


pgsql-general by date:

Previous
From: Jerry Sievers
Date:
Subject: Re: Space Stalker in SQL Output
Next
From: Peter Geoghegan
Date:
Subject: Re: could not read block 0 in file : read only 0 of 8192 bytes whendoing nasty on immutable index function