On Sat, 27 May 2006 13:26:24 -0400 (EDT)
Bruce Momjian 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 writes:
Thank you for your attention. I thought my
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 writes:
> > Your patch has been added to the Post
Bruce Momjian writes:
> Your patch has been added to the PostgreSQL unapplied patches list at:
I don't particularly like this patch, because it is predicated on a
false assumption, namely that initdb uses libpq to talk to the backend.
ISTM PQescapeString is not the thing to use. (As a concrete e
Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.
---
im
Has anyone notice this? I found that this is not fixed in the 8.1.4
release.
I have made a new patch for 8.1.4. It is attached below. Please
tell me if there is any problem. Thank you.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
diff -u -r postgresql-8.1.4.orig/src/bin/initdb/initd
The following bug has been logged online:
Bug reference: 2424
Logged by: imacat
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: Linux
Description:initdb Did Not Escape the Password
Details:
The initdb seems did not escape (PQescapeString
