| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Li EF Zhang <bjzhangl(at)cn(dot)ibm(dot)com> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Can not ALTER TEXT SEARCH DICTIONARY intdict which is default in dict_int |
| Date: | 2021-08-25 04:01:07 |
| Message-ID: | CAKFQuwYHO8=5MjpUJgmLCJTz_okaUWVVqADhcJ84tukMTEATqg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Aug 24, 2021 at 8:51 PM Li EF Zhang <bjzhangl(at)cn(dot)ibm(dot)com> wrote:
> Thanks for your answer. My doubt is that since an ordinary user creates
> the extension, shouldn't be this user the owner of the objects created
> within the extension?
>
While that is a possible implementation choice, that isn't what was chosen.
https://www.postgresql.org/docs/current/sql-createextension.html
"This configuration gives the calling user the right to drop the extension,
but not to modify individual objects within it."
"trust" just solves the "lets not require an actual superuser to install a
superuser requiring extension" problem, if that extension is deemed safe to
use in that manner by its author.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-08-25 04:19:55 | Re: Can not ALTER TEXT SEARCH DICTIONARY intdict which is default in dict_int |
| Previous Message | Li EF Zhang | 2021-08-25 03:51:38 | RE: Can not ALTER TEXT SEARCH DICTIONARY intdict which is default in dict_int |