Re: fix and document CLUSTER privileges
От
Nathan Bossart
Тема
Re: fix and document CLUSTER privileges
Дата
Msg-id
20230105171142.GA299579@nathanxps13
Ответ на
Re: fix and document CLUSTER privileges (Gilles Darold)
Список
Дерево обсуждения
fix and document CLUSTER privileges Nathan Bossart <nathandbossart@gmail.com>
Re: fix and document CLUSTER privileges Justin Pryzby <pryzby@telsasoft.com>
Re: fix and document CLUSTER privileges Nathan Bossart <nathandbossart@gmail.com>
Re: fix and document CLUSTER privileges Andrew Dunstan <andrew@dunslane.net>
Re: fix and document CLUSTER privileges Nathan Bossart <nathandbossart@gmail.com>
Re: fix and document CLUSTER privileges Robert Haas <robertmhaas@gmail.com>
Re: fix and document CLUSTER privileges Nathan Bossart <nathandbossart@gmail.com>
Re: fix and document CLUSTER privileges Nathan Bossart <nathandbossart@gmail.com>
Re: fix and document CLUSTER privileges Gilles Darold <gilles@migops.com>
Re: fix and document CLUSTER privileges Nathan Bossart <nathandbossart@gmail.com>
Re: fix and document CLUSTER privileges Gilles Darold <gilles@migops.com>
Re: fix and document CLUSTER privileges Nathan Bossart <nathandbossart@gmail.com>
Re: fix and document CLUSTER privileges Gilles Darold <gilles@migops.com>
Re: fix and document CLUSTER privileges Nathan Bossart <nathandbossart@gmail.com>
Re: fix and document CLUSTER privileges Nathan Bossart <nathandbossart@gmail.com>
Re: fix and document CLUSTER privileges Gilles Darold <gilles@migops.com>
Re: fix and document CLUSTER privileges Nathan Bossart <nathandbossart@gmail.com>
Re: fix and document CLUSTER privileges Gilles Darold <gilles@migops.com>
Re: fix and document CLUSTER privileges Nathan Bossart <nathandbossart@gmail.com>
Re: fix and document CLUSTER privileges Jeff Davis <pgsql@j-davis.com>
Re: fix and document CLUSTER privileges Nathan Bossart <nathandbossart@gmail.com>
Re: fix and document CLUSTER privileges Pavel Luzanov <p.luzanov@postgrespro.ru>
On Thu, Jan 05, 2023 at 02:38:58PM +0100, Gilles Darold wrote: > This is a bit confusing, this commitfest entry patch is also included in an > other commitfest entry [1] into patch v3-0001-fix-maintain-privs.patch with > some additional conditions. > > Committers should be aware that this commitfest entry must be withdrawn if > [1] is committed first. There is no status or dependency field that I can > use, I could move this one to "Ready for Committer" status but this is not > exact until [1] has been committed or withdrawn. I will either rebase the other patch or discard this one as needed. I'm not positive that we'll proceed with the proposed approach for the other one, but the patch tracked here should still be worthwhile regardless. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com
В списке pgsql-hackers по дате отправления