| From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: tsearch_core patch: permissions and security issues |
| Date: | 2007-06-14 18:52:57 |
| Message-ID: | 46718E89.4030508@sigaev.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
>> But they still need some more thought about permissions, because AFAICS
>> mucking with a configuration can invalidate some other user's data.
>
> ouch. could mucking with a configuration create a corrupt index?
Depending on what you mean 'corrupted'. It will not corrupted as non-readable
or cause backend crash. But usage of such tsvector column could be limited - not
all words will be searchable.
> This sounds sort of analogous to the issues collation bring up.
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-06-14 18:54:07 | Re: tsearch_core patch: permissions and security issues |
| Previous Message | Teodor Sigaev | 2007-06-14 18:48:11 | Re: tsearch_core patch: permissions and security issues |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-06-14 18:54:07 | Re: tsearch_core patch: permissions and security issues |
| Previous Message | Teodor Sigaev | 2007-06-14 18:48:11 | Re: tsearch_core patch: permissions and security issues |