| From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
|---|---|
| To: | MURAT KOÇ <m(dot)koc21(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Changing Passwords as Encrypted not Clear-Text |
| Date: | 2011-12-19 22:59:02 |
| Message-ID: | 201112191459.03059.adrian.klaver@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Monday, December 19, 2011 11:46:05 am MURAT KOÇ wrote:
> Hi Adrian,
>
> Both of advices that are using md5 algorithm and setting log_statement for
> session specific worked well.
>
> Thanks for suggestions and solution advices.
Glad it worked. A thought came to mind just now. If you decide to use the SET
method you may also want to look at the error configuration settings also.
Should there be a mistake in the SQL statement it is possible the password would
show up in an ERROR message.
>
> Best Regards,
> Murat KOC
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Louis-David Mitterrand | 2011-12-20 09:05:41 | using pg's internal timezone database? |
| Previous Message | Hannes Erven | 2011-12-19 21:46:36 | Re: Feature Request: Better handling of foreign keys in DELETE statements |