| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thom Brown <thombrown(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, PGSQL Mailing List <pgsql-general(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Updating column on row update |
| Date: | 2009-11-23 14:38:34 |
| Message-ID: | 13302.1258987114@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Thom Brown <thombrown(at)gmail(dot)com> writes:
> As for having plpgsql installed by default, are there any security
> implications?
Well, that's pretty much exactly the question --- are there? It would
certainly make it easier for someone to exploit any other security
weakness they might find. I believe plain SQL plus SQL functions is
Turing-complete, but that doesn't mean it's easy or fast to write loops
etc in it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thom Brown | 2009-11-23 15:05:14 | Re: [HACKERS] Updating column on row update |
| Previous Message | Robert Haas | 2009-11-23 14:31:50 | Re: [HACKERS] Updating column on row update |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Emmanuel Cecchet | 2009-11-23 14:39:33 | Re: Partitioning option for COPY |
| Previous Message | Robert Haas | 2009-11-23 14:31:50 | Re: [HACKERS] Updating column on row update |