Ezra Epstein wrote:
> I'd like to extend SET SESSION AUTHORIZATION to support a form which takes a
> password. Looking at the source it seems, other than changes to the parser,
> there are only 2 relevant functions in 2 files that would be affected. Each
> function is quite small and its function is clear.
> I did not find this functionality on the current to-do list:
> And I'm quite new to the PG backend. I don't want to code something up that
> is unwelcome by the developers. On the other hand, if appropriate/accepted,
> I'd be glad to write this little addition to the current functionality.
[ CC to hackers added.]
Uh, a password? What purpose would that serve? Isn't that something
you control when attaching to the database? Is this for prompting for
a username password? The problem is that the SQL query passing isn't
secure like the way we send passwords using libpq, so I don't think this
would be secure or wise to hardcode a password in the SQL.
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2004-01-27 03:56:24|
|Subject: Re: Extending SET SESSION AUTHORIZATION |
|Previous:||From: Bruce Momjian||Date: 2004-01-27 01:53:02|
|Subject: Re: What's left?|