Thread: pgsql-server/ oc/src/sgml/libpq++.sgml oc/src/ ...

pgsql-server/ oc/src/sgml/libpq++.sgml oc/src/ ...

From
momjian@postgresql.org (Bruce Momjian - CVS)
Date:
CVSROOT:    /cvsroot
Module name:    pgsql-server
Changes by:    momjian@postgresql.org    02/08/14 22:56:19

Modified files:
    doc/src/sgml   : libpq++.sgml libpq.sgml
    src/interfaces/libpq: fe-connect.c
    src/interfaces/perl5: Pg.pm

Log message:
    I'm giving a try at some TODO items.  Currently it's the turn of the
    PGPASSWORDFILE environment variable.  I have modified libpq to make use
    of this variable.  I present the first cut here.

    Currently the format for the file should be

    host:port:database:user:password

    Alvaro Herrera


Re: pgsql-server/ oc/src/sgml/libpq++.sgml oc/src/ ...

From
Tom Lane
Date:
momjian@postgresql.org (Bruce Momjian - CVS) writes:
>     I'm giving a try at some TODO items.  Currently it's the turn of the
>     PGPASSWORDFILE environment variable.  I have modified libpq to make use
>     of this variable.  I present the first cut here.

You applied the *first* cut?  That patch went through two or three
revisions IIRC ...

            regards, tom lane

Re: pgsql-server/ oc/src/sgml/libpq++.sgml oc/src/ ...

From
Bruce Momjian
Date:
No, I applied the final one, but CVS shows the text of the first patch
because that is the only one that has the full description.  The email
saying the patch was applied has the actual text of the patch applied:

---------------------------------------------------------------------------

Patch applied.  Thanks.

---------------------------------------------------------------------------

Alvaro Herrera wrote:
> Larry Rosenman dijo:
>
> > On Sun, 2002-08-11 at 15:45, Tom Lane wrote:
> > > Alvaro Herrera <alvherre@atentus.com> writes:
> > > > I attach a patch that adds the PGPASSWORDFILE ability to libpq,
and
> > > > removes the use of PGPASSWORD.
> > >
> > > Were we actually going to *remove* that, as opposed to deprecate
it?
> > >
> > > There are systems (in fact many) where it's perfectly secure, so
I'm
> > > not that thrilled about removing functionality ...
>
> > PLEASE DO NOT REMOVE IT WITHOUT AT LEAST ONE RELEASE CYCLE WARNING.
> >
> > You will ****BREAK**** People.
>
> Ok, advice taken.  New patch attached.  Preserves the ability to use
> PGPASSWORD, which in fact has preference over PGPASSWORDFILE.
>
> --
> Alvaro Herrera (<alvherre[a]atentus.com>)
> www.google.com: interfaz de linea de comando para la web.

---------------------------------------------------------------------------

Tom Lane wrote:
> momjian@postgresql.org (Bruce Momjian - CVS) writes:
> >     I'm giving a try at some TODO items.  Currently it's the turn of the
> >     PGPASSWORDFILE environment variable.  I have modified libpq to make use
> >     of this variable.  I present the first cut here.
>
> You applied the *first* cut?  That patch went through two or three
> revisions IIRC ...
>
>             regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073