Josh Berkus wrote: > As such, proposals are more likely to be successful if the proposer can > show how they apply to a general use case, or adapt them so that they > are useful to a large number of our users. This means that "this works > in our environment which has conditions X, Y, and Z" is not an effective > argument, unless you can follow it up with "... and here's the reason > why [large class of users] also has conditions X, Y and Z."
The proposal here is to have a configure argument that disables arbitrary auth mechanisms. How is that specific to a particular environment? -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
