Re: Read access for pg_monitor to pg_replication_origin_status view
От
Tom Lane
Тема
Re: Read access for pg_monitor to pg_replication_origin_status view
Дата
Msg-id
1098356.1592196242@sss.pgh.pa.us
Ответ на
Re: Read access for pg_monitor to pg_replication_origin_status view (Michael Paquier)
Список
Дерево обсуждения
Read access for pg_monitor to pg_replication_origin_status view Martín Marqués <martin@2ndquadrant.com>
Re: Read access for pg_monitor to pg_replication_origin_status view Martín Marqués <martin@2ndquadrant.com>
Re: Read access for pg_monitor to pg_replication_origin_status view Michael Paquier <michael@paquier.xyz>
Re: Read access for pg_monitor to pg_replication_origin_status view Martín Marqués <martin@2ndquadrant.com>
Re: Read access for pg_monitor to pg_replication_origin_status view Martín Marqués <martin@2ndquadrant.com>
Re: Read access for pg_monitor to pg_replication_origin_status view Michael Paquier <michael@paquier.xyz>
Re: Read access for pg_monitor to pg_replication_origin_status view Martín Marqués <martin@2ndquadrant.com>
Re: Read access for pg_monitor to pg_replication_origin_status view Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Re: Read access for pg_monitor to pg_replication_origin_status view Martín Marqués <martin@2ndquadrant.com>
Re: Read access for pg_monitor to pg_replication_origin_status view Stephen Frost <sfrost@snowman.net>
Re: Read access for pg_monitor to pg_replication_origin_status view Martín Marqués <martin@2ndquadrant.com>
Re: Read access for pg_monitor to pg_replication_origin_status view Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Re: Read access for pg_monitor to pg_replication_origin_status view Martín Marqués <martin@2ndquadrant.com>
Re: Read access for pg_monitor to pg_replication_origin_status view Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Re: Read access for pg_monitor to pg_replication_origin_status view Martín Marqués <martin@2ndquadrant.com>
Re: Read access for pg_monitor to pg_replication_origin_status view Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Re: Read access for pg_monitor to pg_replication_origin_status view Masahiko Sawada <masahiko.sawada@2ndquadrant.com>
Re: Read access for pg_monitor to pg_replication_origin_status view Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Re: Read access for pg_monitor to pg_replication_origin_status view Michael Paquier <michael@paquier.xyz>
Re: Read access for pg_monitor to pg_replication_origin_status view Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Re: Read access for pg_monitor to pg_replication_origin_status view Masahiko Sawada <masahiko.sawada@2ndquadrant.com>
Re: Read access for pg_monitor to pg_replication_origin_status view Michael Paquier <michael@paquier.xyz>
Re: Read access for pg_monitor to pg_replication_origin_status view Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Re: Read access for pg_monitor to pg_replication_origin_status view Masahiko Sawada <masahiko.sawada@2ndquadrant.com>
Re: Read access for pg_monitor to pg_replication_origin_status view Michael Paquier <michael@paquier.xyz>
Re: Read access for pg_monitor to pg_replication_origin_status view Michael Paquier <michael@paquier.xyz>
Re: Read access for pg_monitor to pg_replication_origin_status view Tom Lane <tgl@sss.pgh.pa.us>
Re: Read access for pg_monitor to pg_replication_origin_status view Michael Paquier <michael@paquier.xyz>
Re: Read access for pg_monitor to pg_replication_origin_status view Daniel Gustafsson <daniel@yesql.se>
Re: Read access for pg_monitor to pg_replication_origin_status view Michael Paquier <michael@paquier.xyz>
Re: Read access for pg_monitor to pg_replication_origin_status view Martín Marqués <martin.marques@gmail.com>
Michael Paquier writes: > On Wed, Jun 10, 2020 at 12:35:49PM +0900, Michael Paquier wrote: >> OK, thanks. Then let's wait a couple of days to see if anybody has >> any objections with the removal of the hardcoded superuser check >> for those functions. > Committed the part removing the superuser checks as of cc07264. FWIW, I'd have included a catversion bump in this, to enforce that the modified backend functions are used with matching pg_proc entries. It's not terribly important at this phase of the devel cycle, but still somebody might wonder why the regression tests are failing for them (if they tried to skip an initdb). regards, tom lane
В списке pgsql-hackers по дате отправления