[BUGS] BUG #4588: post gres installation problem

[raghavendra]

The following bug has been logged online:

Bug reference:  4588
Logged by:  raghavendra
Email address:  raghavend...@integramicro.com
PostgreSQL version: 8.3
Operating system:   windows 2003 standard edition with sp2
Description:post gres installation problem
Details: 

When we install postgres as a service with postgressql account it says user
not have a sufficient privilege to run as a service"

If not selected run as a service it will install first stage while second
stage it fails create database

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

[BUGS] Problem with PostGreSQL 7.4.2 on HPUX 11.11(700 PARISC Systems)

[Raghavendra HR]

Hello,

I have problem while configuring the PostGreSQL 7.4.2 on HPUX 11.11
(PARISC).
I am starting the configuration with the belwo command.
./configure --prefix=/usr/local/pgsql --without-readline --without-zlib

.**Starts the configurations
NOW.**
checking build system type... hppa2.0w-hp-hpux11.11
checking host system type... hppa2.0w-hp-hpux11.11
checking which template to use... hpux
checking whether to build with 64-bit integer date/time support... no
checking whether NLS is wanted... no
checking for default port number... 5432
checking for gcc... no
checking for cc... cc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... no
checking whether cc accepts -g... yes
checking how to turn off strict aliasing in cc -Ae...
configure: using CFLAGS=+O2
checking whether the C compiler still works... yes
checking how to run the C preprocessor... cc -Ae -E
checking allow thread-safe client libraries... no
checking whether to build with Tcl... no
checking whether to build with Tk... no
checking whether to build Perl modules... no
checking whether to build Python modules... no
checking whether to build Java/JDBC tools... no
checking whether to build with Kerberos 4 support... no
checking whether to build with Kerberos 5 support... no
checking whether to build with PAM support... no
checking whether to build with Rendezvous support... no
configure: using CPPFLAGS=-D_XOPEN_SOURCE_EXTENDED
configure: using LDFLAGS=
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking for flex... no
configure: WARNING:
*** Without Flex you will not be able to build PostgreSQL from CVS or
*** change any of the scanner definition files.  You can obtain Flex from
*** a GNU mirror site.  (If you are using the official distribution of
*** PostgreSQL then you do not need to worry about this because the Flex
*** output is pre-generated.)
checking whether ln -s works... yes
checking for non-GNU ld... /bin/ld
checking if the linker (/bin/ld) is GNU ld... no
checking for ranlib... ranlib
checking for lorder... lorder
checking for tar... /bin/tar
checking for strip... strip
checking whether it is possible to strip libraries... no
checking for bison... no
configure: WARNING:
*** Without Bison you will not be able to build PostgreSQL from CVS or
*** change any of the parser definition files.  You can obtain Bison from
*** a GNU mirror site.  (If you are using the official distribution of
*** PostgreSQL then you do not need to worry about this because the Bison
*** output is pre-generated.)  To use a different yacc program (possible,
*** but not recommended), set the environment variable YACC before running
*** 'configure'.
checking for perl... /bin/perl
checking for main in -lbsd... no
checking for setproctitle in -lutil... no
checking for main in -lm... yes
checking for main in -ldl... no
checking for main in -lnsl... yes
checking for main in -lsocket... no
checking for main in -lipc... no
checking for main in -lIPC... no
checking for main in -llc... no
checking for main in -ldld... yes
checking for main in -lld... no
checking for main in -lcompat... no
checking for main in -lBSD... yes
checking for main in -lgen... yes
checking for main in -lPW... yes
checking for main in -lresolv... no
checking for library containing getopt_long... no
checking for main in -lunix... no
checking for library containing crypt... none required
checking for library containing fdatasync... none required
checking for shmget in -lcygipc... no
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... no
checking for unistd.h... yes
checking crypt.h usability... yes
checking crypt.h presence... yes
checking for crypt.h... yes
checking dld.h usability... no
checking dld.h presence... no
checking for dld.h... no
checking endian.h usability... no
checking endian.h presence... no
checking for endian.h... no
checking fp_class.h usability... no
checking fp_class.h presence... no
checking for fp_class.h... no
checking getopt.h usability... no
checking getopt.h presence... no
checking for getopt.h... no
checking ieeefp.h usability... no
checking ieeefp.h presence... no
checking for ieeefp.h... no
checking poll.h usability... yes
checking poll.h presence... yes
checking for poll.h... yes
checking pwd.h usability... yes
checking pwd.h presence... yes
checking for pwd.h... yes
checking sys/ipc.h usability... yes
checking sys/ipc.h presence... yes
checking for sys/ipc.h... yes
checking sys/poll.h usability... yes
checking sys/poll.h presence... yes
checking for sys/poll.

[BUGS] BUG #8438: Usage of Pipe operator in Windows(CMD.exe) shows the password typed with any PG utility.

[raghavendra . rao]

The following bug has been logged on the website:

Bug reference:  8438
Logged by:  Raghav
Email address:  raghavendra@enterprisedb.com
PostgreSQL version: 9.2.2
Operating system:   Windows
Description:

Hi,


I have PostgreSQL 9.2 instance on Windows 7 running in MD5 authentication
mode. Anytime I connect I need to pass the password for connection. When I
try to connect from command prompt using PIPE ('|") operator; and the
password I type is visible(shown) instead of hiding it. For example in
linux, any password typed when prompted will not show it just hides it.
Which seems not the same in windows. Please look at the example below:


1. Go to command prompt (runas /user:postgres "cmd.exe")


2. Pass the some command using pipe operator to Psql (or any utility).


c:\Program Files\PostgreSQL\9.2\bin>echo select version(); | psql -p 5433
Password: postgres


   version
-
 PostgreSQL 9.2.2, compiled by Visual C++ build 1600, 32-bit
(1 row)


If you see above output, the password I typed as "postgres" is clearly
visible. I didn't tried to reproduce on any other version of PG or Windows.
Below are my version details:


Operating System: Windows 7 64 bit
PostgreSQL: PostgreSQL 9.2.2


For any further information required, I would be glad to share if its sent
to my email id: raghavendra@enterprisedb.com.


Thank you .
 
---
Regards,
Raghavendra
EnterpriseDB Corporation



-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs