| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: tsearch_core patch: permissions and security issues |
| Date: | 2007-06-14 17:43:15 |
| Message-ID: | 16291.1181842995@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> Well my argument has always been the "core" feature argument. Perhaps I
> am missing some info here, but when I read what you wrote, I read that
> Tsearch will now be "harder" to work with. Not easier. :(
Then you misread it. What I was proposing was essentially that there
won't be any need for pg_dump support because everything's built-in
(at least as far as parsers/dictionaries go).
As for the permissions issues, that's just formalizing something that's
true today with the contrib module: if you change a configuration, it's
*your* problem whether that invalidates any table entries, the system
won't take care of it for you.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2007-06-14 17:45:31 | Re: tsearch_core patch: permissions and security issues |
| Previous Message | Joshua D. Drake | 2007-06-14 17:38:05 | Re: tsearch_core patch: permissions and security issues |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2007-06-14 17:45:31 | Re: tsearch_core patch: permissions and security issues |
| Previous Message | Joshua D. Drake | 2007-06-14 17:38:05 | Re: tsearch_core patch: permissions and security issues |