pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: tushar <tushar.ahuja@enterprisedb.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Antje Petersen <antje.petersen@desy.de>
Cc: pgsql-bugs@postgresql.org
Subject: Re: BUG #5814: documentation bug
Date: Fri, 11 Mar 2011 20:26:21 +0530
Message-ID: <4D7A3815.5020605@enterprisedb.com> (raw)
In-Reply-To: <201103111444.p2BEiqj02720@momjian.us>
References: <201103111444.p2BEiqj02720@momjian.us>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bruce Momjian wrote:

> Well, what do you suggest?  I see no other way to specify the default
> for pressing <ENTER>.  I know I just press <ENTER> at those prompts.
> 

[root@tushar bin]# ./createuser -p 5438
Enter name of role to add: test
Shall the new role be a superuser? (y/n)
Please answer "y" or "n".
Shall the new role be a superuser? (y/n)

even if i just <<enter>> it is still asking me to enter 'y' or 'n'

i m using pg9.0 beta3

[root@tushar bin]# ./psql postgres -U postgres -p 5438
Password for user postgres:
psql (9.0beta3)
Type "help" for help.

postgres=#

i think it should show like this :-(if n is the default)

[root@tushar bin]# ./createuser -p 5438
Enter name of role to add: test
Shall the new role be a superuser? (y/N)
Shall the new role be allowed to create more new roles? (y/N)


but don't know how it is behaving in PG 8.1 (as this issue reported against that version)


- --
regards,tushar
Lead QA Engineer
EnterpriseDB Corporation
The Enterprise PostgreSQL Company

Mobile: +91-99227433-47

This e-mail message (and any attachment) is intended for the use of
the individual or entity to whom it is addressed. This message
contains information from EnterpriseDB Corporation that may be
privileged, confidential, or exempt from disclosure under applicable
law. If you are not the intended recipient or authorized to receive
this for the intended recipient, any use, dissemination, distribution,
retention, archiving, or copying of this communication is strictly
prohibited. If you have received this e-mail in error, please notify
the sender immediately by reply e-mail and delete this message


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFNejgVfQNodY2PIRoRAtXVAJ9xa6OKelV5dqmwW+bBTSFwhtxsNACgjtjx
F0MwcsLqhrC8gD+GOQNgpgs=
=loHA
-----END PGP SIGNATURE-----



view thread (10+ messages)  latest in thread

Message-ID: <4D7A3815.5020605@enterprisedb.com>
Permalink:  ../4D7A3815.5020605@enterprisedb.com/
Also on:    postgresql.org/message-id/4D7A3815.5020605@enterprisedb.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: tushar.ahuja@enterprisedb.com, bruce@momjian.us, robertmhaas@gmail.com, antje.petersen@desy.de, pgsql-bugs@postgresql.org
  Subject: Re: BUG #5814: documentation bug
  In-Reply-To: <4D7A3815.5020605@enterprisedb.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox