Horton

Re: Functions 'is_publishable_class' and 'is_publishable_relation' should stay together.

Peter Smith <smithpb2250@gmail.com>

View thread View on postgr.es
From: Peter Smith <smithpb2250@gmail.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Amit Kapila <amit.kapila16@gmail.com>, "houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-07-29T09:51:07Z
Lists: pgsql-hackers 
On Fri, Jul 29, 2022 at 7:36 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
>
> On 2022-Jul-29, Peter Smith wrote:
>
> > PSA v2 of this patch, modified as suggested.
>
> I don't object to doing this, but I think these two functions should
> stay together nonetheless.


Hmm, I think there is some confusion because different people have
mentioned multiple functions.

AFAIK, the patch *does* ensure the 2 functions (is_publishable_class
and is_publishable_relation) stay together.

If you believe there is still a problem after applying the patch
please explicitly name what function(s) you think should be moved.

------
Kind Regards,
Peter Smith.
Fujitsu Australia

Commits

  1. Move common catalog cache access routines to lsyscache.c

  2. Move related functions next to each other in pg_publication.c.

  3. Allow publishing the tables of schema.

  4. Allow GRANT on pg_log_backend_memory_contexts().