| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Joe Conway <mail(at)joeconway(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: MAINTAIN privilege -- what do we need to un-revert it? |
| Date: | 2024-02-17 00:03:55 |
| Message-ID: | 4d497d82e4516037dc1082d5a62d199ea00d62e7.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2024-02-14 at 13:02 -0600, Nathan Bossart wrote:
> This seemed like the approach folks were most in favor of at the
> developer
> meeting a couple weeks ago [0]. At least, that was my interpretation
> of
> the discussion.
Attached rebased version.
Note the changes in amcheck. It's creating functions and calling those
functions from the comparators, and so the comparators need to set the
search_path. I don't think that's terribly common, but does represent a
behavior change and could break something.
Regards,
Jef Davis
| Attachment | Content-Type | Size |
|---|---|---|
| v4-0001-Fix-search_path-to-a-safe-value-during-maintenanc.patch | text/x-patch | 26.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2024-02-17 00:31:07 | Re: Add bump memory context type and use it for tuplesorts |
| Previous Message | Tom Lane | 2024-02-16 23:14:44 | Re: Add bump memory context type and use it for tuplesorts |