Re: pgsql: Fix search_path to a safe value during maintenance operations.
| От | Jeff Davis |
|---|---|
| Тема | Re: pgsql: Fix search_path to a safe value during maintenance operations. |
| Дата | |
| Msg-id | 931c23465c331fc3d53073cdefa53bad464b0469.camel@j-davis.com обсуждение исходный текст |
| Ответ на | Re: pgsql: Fix search_path to a safe value during maintenance operations. (Nathan Bossart <nathandbossart@gmail.com>) |
| Ответы |
Re: pgsql: Fix search_path to a safe value during maintenance operations.
|
| Список | pgsql-hackers |
On Thu, 2023-06-29 at 22:09 -0700, Nathan Bossart wrote:
> On Thu, Jun 29, 2023 at 08:53:56PM -0400, Tom Lane wrote:
> > I'm leaning to Robert's thought that we need to revert this for
> > now,
> > and think harder about how to make it work cleanly and safely.
>
> Since it sounds like this is headed towards a revert, here's a patch
> for
> removing MAINTAIN and pg_maintain.
It was difficult to review standalone, so I tried a quick version
myself and ended up with very similar results. The only substantial
difference was that I put back:
+ if (!vacuum_is_relation_owner(relid, classForm,
options))
+ continue;
in get_all_vacuum_rels() whereas your patch left it out -- double-check
that we're doing the right thing there.
Also remember to bump the catversion. Other than that, it looks good to
me.
Regards,
Jeff Davis
В списке pgsql-hackers по дате отправления: