[BUGS] Bug #756: suggestion: file with password instead of $PGPASSWORD
Wojciech Scigala ([EMAIL PROTECTED]) reports a bug with a severity of 4 The lower the number the more severe it is. Short Description suggestion: file with password instead of $PGPASSWORD Long Description This is not a bug-report in fact, but a suggestion of a feature. (I couldn't find an separate email for suggestions and ideas). As you know, many people have trouble keeping both secure (passworded) access to PG databased while allowing some unattended access for them, for example for backing up. Enviroment variable $PGPASSWORD is very useful here, but sensitive data should not be passed via enviroment. The better way to do it is to provide a name of file which contains the password. The file's access rights (if set properly) will provide necessary security in an easy way. And that's what I'm suggesting - an introdution of new variable, say $PGPASSWORD_FILE which will point to a file with password. Sample Code No file was uploaded with this report ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [BUGS] Bug #756: suggestion: file with password instead of
This item: Add file to hold passwords using PGPASSWORDFILE environment variable Has been completed, and will be a part of the 7.3 release. Thanks, Rod On Wed, 2002-09-04 at 11:54, [EMAIL PROTECTED] wrote: > Wojciech Scigala ([EMAIL PROTECTED]) reports a bug with a severity of 4 > The lower the number the more severe it is. > > Short Description > suggestion: file with password instead of $PGPASSWORD > > Long Description > This is not a bug-report in fact, but a suggestion of a feature. > (I couldn't find an separate email for suggestions and ideas). > As you know, many people have trouble keeping both secure (passworded) access to PG >databased while allowing some unattended access for them, for example for backing up. > Enviroment variable $PGPASSWORD is very useful here, but sensitive data should not >be passed via enviroment. The better way to do it is to provide a name of file which >contains the password. The file's access rights (if set properly) will provide >necessary security in an easy way. And that's what I'm suggesting - an introdution of >new variable, say $PGPASSWORD_FILE which will point to a file with password. > > Sample Code > > > No file was uploaded with this report > > > ---(end of broadcast)--- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org > ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [BUGS] Bug #756: suggestion: file with password instead of $PGPASSWORD
This functionality will be in 7.3, due out in a few months. --- [EMAIL PROTECTED] wrote: > Wojciech Scigala ([EMAIL PROTECTED]) reports a bug with a severity of 4 > The lower the number the more severe it is. > > Short Description > suggestion: file with password instead of $PGPASSWORD > > Long Description > This is not a bug-report in fact, but a suggestion of a feature. > (I couldn't find an separate email for suggestions and ideas). > As you know, many people have trouble keeping both secure (passworded) access to PG >databased while allowing some unattended access for them, for example for backing up. > Enviroment variable $PGPASSWORD is very useful here, but sensitive data should not >be passed via enviroment. The better way to do it is to provide a name of file which >contains the password. The file's access rights (if set properly) will provide >necessary security in an easy way. And that's what I'm suggesting - an introdution of >new variable, say $PGPASSWORD_FILE which will point to a file with password. > > Sample Code > > > No file was uploaded with this report > > > ---(end of broadcast)--- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org > -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[BUGS] Bug #757: ODBC Doesn works
Lazaro ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description ODBC Doesn works Long Description I have Postgresql 7.2.2 in a red hat 7.3 machine. I'm programming in a PowerBuilder 8.0 in a windows 2000 machine, I have a PSQLODBC-07-02-0002. When I try to access to the Postgres with ODBC, PowerBuilder crash with an exeption code, and It doesn't occur with SQL SERVER. The outpus is: conn=66992464, query='select pbe_name, pbe_edit, pbe_type, pbe_cntr, pbe_work, pbe_seqn, pbe_flag from "postgres".pbcatedt order by pbe_name, pbe_seqn' ERROR from backend during send_query: 'ERROR: parser: parse error at or near "."' STATEMENT ERROR: func=SC_execute, desc='', errnum=7, errmsg='Error while executing the query' hdbc=66992464, stmt=66986264, result=67013344 manual_result=0, prepare=0, internal=0 bindings=0, bindings_allocated=0 parameters=0, parameters_allocated=0 statement_type=0, statement='select pbe_name, pbe_edit, pbe_type, pbe_cntr, pbe_work, pbe_seqn, pbe_flag from "postgres".pbcatedt order by pbe_name, pbe_seqn' The user name with I conect with the database is postgres, but It occur in the same way with any user If I access with pgadmin-1.0.2 in the same machine, I have no problem Sample Code No file was uploaded with this report ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [BUGS] Bug #757: ODBC Doesn works
On Wed, 4 Sep 2002 [EMAIL PROTECTED] wrote: > Long Description > I have Postgresql 7.2.2 in a red hat 7.3 machine. I'm programming in a > PowerBuilder 8.0 in a windows 2000 machine, I have a > PSQLODBC-07-02-0002. When I try to access to the Postgres with ODBC, > PowerBuilder crash with an exeption code, and It doesn't occur with > SQL SERVER. > > The outpus is: > > conn=66992464, query='select pbe_name, pbe_edit, pbe_type, pbe_cntr, > pbe_work, pbe_seqn, pbe_flag from "postgres".pbcatedt order by > pbe_name, pbe_seqn' That's not a legal query to 7.2.2 afaict. It's presumably erroring due to the "postgres".pbcatedt. I think you'd want to drop the "postgres". portion of the query to make it work. ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[BUGS] Schemas not available for pl/pgsql %TYPE....
Call me crazy, but shouldn't the following work? :~| CREATE FUNCTION t() RETURNS TEXT AS ' DECLARE col_name pg_catalog.pg_attribute.attname%TYPE; BEGIN col_name := ''uga''; RETURN col_name; END; ' LANGUAGE 'plpgsql'; CREATE FUNCTION SELECT t(); WARNING: plpgsql: ERROR during compile of t near line 2 ERROR: Invalid type name 'pg_catalog.pg_attribute.attname % TYPE' -sc -- Sean Chittenden msg04760/pgp0.pgp Description: PGP signature
Re: [BUGS] Schemas not available for pl/pgsql %TYPE....
Sean Chittenden <[EMAIL PROTECTED]> writes: > Call me crazy, but shouldn't the following work? :~| Sure should. Want to fix plpgsql's parser? regards, tom lane ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [BUGS] Schemas not available for pl/pgsql %TYPE....
> Sean Chittenden <[EMAIL PROTECTED]> writes: > > Call me crazy, but shouldn't the following work? :~| > > Sure should. Want to fix plpgsql's parser? Why not: I've never been one to avoid strapping on 4tons in rocks and jumping into the deep end. ::sigh:: Is it me or does it look like all of pl/pgsql is schema un-aware (ie, all of the declarations). -sc -- Sean Chittenden ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [BUGS] Schemas not available for pl/pgsql %TYPE....
Sean Chittenden <[EMAIL PROTECTED]> writes: > ::sigh:: Is it me or does it look like all > of pl/pgsql is schema un-aware (ie, all of the declarations). -sc Yeah. The group of routines parse_word, parse_dblword, etc that are called by the lexer certainly all need work. There are some definitional issues to think about, too --- plpgsql presently relies on the number of names to give it some idea of what to look for, and those rules are probably all toast now. Please come up with a sketch of what you think the behavior should be before you start hacking code. regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [BUGS] Schemas not available for pl/pgsql %TYPE....
Tom Lane wrote: > Sean Chittenden <[EMAIL PROTECTED]> writes: > > ::sigh:: Is it me or does it look like all > > of pl/pgsql is schema un-aware (ie, all of the declarations). -sc > > Yeah. The group of routines parse_word, parse_dblword, etc that are > called by the lexer certainly all need work. There are some > definitional issues to think about, too --- plpgsql presently relies on > the number of names to give it some idea of what to look for, and those > rules are probably all toast now. Please come up with a sketch of what > you think the behavior should be before you start hacking code. Added to TODO: o Make PL/PgSQL %TYPE schema-aware -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
