| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alex Hunsaker <badalex(at)gmail(dot)com> |
| Cc: | Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, jd(at)commandprompt(dot)com, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Safe security |
| Date: | 2010-03-08 20:16:04 |
| Message-ID: | 22156.1268079364@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alex Hunsaker <badalex(at)gmail(dot)com> writes:
> That being said I would be in favor of at least saying "Hey! your
> using a known broken version of Safe". Maybe something like the below
> at pl_perl init time? (That is instead of requiring >v2.25 just
> complain about older versions)
> elog(WARNING, "Safe versions before 2.25 have known issues. Please
> consider upgrading.");
We're in the service of providing a tool, not a nanny.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-03-08 20:25:43 | Re: SQL compatibility reminder: MySQL vs PostgreSQL |
| Previous Message | Alex Hunsaker | 2010-03-08 18:11:07 | Re: Safe security |