Patch added to current open commitfest under the Client section with title:
"Call \pset without any arguments displays current status of all
printing options"
Status: Need review.
Let me know if it should not be there.
Regards,
Le 29/06/2013 01:08, Gilles Darold a écrit :
> Hi,
>
> I was lo
Le 29/06/2013 13:55, Erik Rijkers a écrit :
> On Sat, June 29, 2013 01:08, Gilles Darold wrote:
>> Here is a sample output:
>>
>> (postgres@[local]:5494) [postgres] > \pset
>> Output format is aligned.
>> Border style is 2.
>> Expanded display is used automatically.
2013/6/29 Erik Rijkers :
> On Sat, June 29, 2013 01:08, Gilles Darold wrote:
>> Here is a sample output:
>>
>> (postgres@[local]:5494) [postgres] > \pset
>> Output format is aligned.
>> Border style is 2.
>> Expanded display is used automatically.
>> Null di
On Sat, June 29, 2013 01:08, Gilles Darold wrote:
> Here is a sample output:
>
> (postgres@[local]:5494) [postgres] > \pset
> Output format is aligned.
> Border style is 2.
> Expanded display is used automatically.
> Null display is "NULL".
> Field s
>Von: pgsql-hackers-ow...@postgresql.org
>[pgsql-hackers-ow...@postgresql.org]" im Auftrag von "Gilles Darold
>[gilles.dar...@dalibo.com]
>I was looking at psql 8.3 documention about \pset options and saw that
>there was the following note :
>
>"Note: It is an error to call \pset without an
Hi,
I was looking at psql 8.3 documention about \pset options and saw that
there was the following note :
"Note: It is an error to call \pset without any arguments. In the
future this case might show the current status of all printing options."
I looked backward and forward to find that this