| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Noah Misch <noah(at)leadboat(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Vaishnavi Prabakaran <vaishnaviprabakaran(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Removal of plaintext password type references |
| Date: | 2017-05-19 21:31:50 |
| Message-ID: | 27279.1495229510@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Thu, May 18, 2017 at 2:37 AM, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
>> I still don't think this worth it to change the hook function's signature
>> for this. Even though it's not a big deal for external modules to adapt,
>> it's not zero effort either. And it's not that much nicer to us.
> I favor committing the proposed patch. Otherwise, it just becomes
> pointless baggage that we carry forever.
> Anyone else want to vote? So far I count 3-1 in favor of making this change.
Actually, on looking at the final form of the patch, it's hard to think
that it's not just useless API churn. The one existing hook user would
have to turn around and call get_password_type() anyway, so it's not
an improvement for that use-case. What's the argument that most other
use-cases wouldn't need to do the same?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Petr Jelinek | 2017-05-19 22:10:21 | Re: Multiple table synchronizations are processed serially |
| Previous Message | Robert Haas | 2017-05-19 21:05:55 | Re: Removal of plaintext password type references |