Skip site navigation (1) Skip section navigation (2)

Re: BUG #2424: initdb Did Not Escape the Password

From: imacat <imacat(at)mail(dot)imacat(dot)idv(dot)tw>
To: PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #2424: initdb Did Not Escape the Password
Date: 2006-05-28 13:51:13
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
On Sat, 27 May 2006 13:26:24 -0400 (EDT)
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> wrote:
> Yes, I was going to rework the patch to use the ideas you suggested.  I
> wasn't going to apply it as-is.  Anyway, feel free to address it.
> Tom Lane wrote:
> > Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:

    Thank you for your attention.  I thought my patch need to be
reworked, too.  I use rather long and complex password for the initial
user "postgres" so that I don't have to remember it.  I do hope this
simple issue could be solved soon.

    And for the path escaping problem, well, almost all Unix
applications have this issue to be solved.  The Perl doesn't work with
an installation prefix with spaces, thus can't be installed into
"C:\Program Files".  I hope this could be solved, too, though I myself
am not in rush need of this.

Best regards,
imacat ^_*' <imacat(at)mail(dot)imacat(dot)idv(dot)tw>
PGP Key:

<<Woman's Voice>> News:
Tavern IMACAT's:
TLUG List Manager:

In response to

pgsql-bugs by date

Next:From: Germán Aracil BonedDate: 2006-05-28 16:45:49
Subject: int64 and spi_getbinval bug !?
Previous:From: Andreas HeidukDate: 2006-05-28 13:17:18
Subject: Too many function calls in view with LEFT JOIN

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group