| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [COMMITTERS] pgsql: Fix an ancient oversight in libpq's handling of V3-protocol COPY |
| Date: | 2008-01-15 21:48:02 |
| Message-ID: | 13815.1200433682@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
I wrote:
> * ParameterStatus could be a risk if a function executed during COPY
> tried to change one of the above-mentioned parameters. Since COPY OUT
> doesn't fire triggers, I think user-defined datatype output functions
> would be the only possible candidates for that.
Scratch that --- that thinking is so last-year :-(. COPY OUT from a
SELECT subquery could fire any old function. pg_dump isn't at risk
from that, but other applications would be.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-01-15 22:00:30 | Re: [COMMITTERS] pgsql: Fix an ancient oversight in libpq's handling of V3-protocol COPY |
| Previous Message | Tom Lane | 2008-01-15 21:45:44 | Re: pgsql: Fix an ancient oversight in libpq's handling of V3-protocol COPY |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-01-15 22:00:30 | Re: [COMMITTERS] pgsql: Fix an ancient oversight in libpq's handling of V3-protocol COPY |
| Previous Message | Tom Lane | 2008-01-15 21:45:44 | Re: pgsql: Fix an ancient oversight in libpq's handling of V3-protocol COPY |