| From: | "Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)com> |
|---|---|
| To: | tgl(at)sss(dot)pgh(dot)pa(dot)us, bruce(at)momjian(dot)us |
| Cc: | pgsql-patches(at)postgresql(dot)org, andrew(at)dunslane(dot)net |
| Subject: | Re: simply custom variables protection |
| Date: | 2007-04-07 17:55:58 |
| Message-ID: | BAY114-F388BF92E857C5C8D456800F95B0@phx.gbl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
>
>Furthermore I believe the patch is incomplete/wrong, because it adds
>only one check on the "armored" flag, whereas PGC_SUSET affects behavior
>in a number of places. I also notice that it will make setting of a
>an armored custom variable from postgresql.conf fail outright in
>non-superuser sessions, which is surely not desirable.
>
I don't protect this patch. I didn't understand original proposal well.
Tom, I don't understand your last notice. Can you explain it, please.
Pavel Stehule
_________________________________________________________________
Citite se osamele? Poznejte nekoho vyjmecneho diky Match.com.
http://www.msn.cz/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-04-07 18:02:24 | Re: simply custom variables protection |
| Previous Message | Bruce Momjian | 2007-04-07 17:51:10 | Re: LIMIT/SORT optimization |