Re: Functions 'is_publishable_class' and 'is_publishable_relation' should stay together.
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Peter Smith <smithpb2250@gmail.com>, "houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-07-29T10:25:10Z
Lists: pgsql-hackers
On Fri, Jul 29, 2022 at 3:29 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: > > On 2022-Jul-29, Peter Smith wrote: > > > On Fri, Jul 29, 2022 at 7:36 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: > > > > > > I don't object to doing this, but I think these two functions should > > > stay together nonetheless. > > > > If you believe there is still a problem after applying the patch > > please explicitly name what function(s) you think should be moved. > > Well, I checked the commit and the functions I was talking about look OK > now. However, looking again, pg_relation_is_publishable is in the wrong > place (should be right below is_publishable_relaton), and I wonder why > aren't get_publication_oid and get_publication_name in lsyscache.c. > Right, both these suggestions make sense to me. Similarly, I think functions get_subscription_name and get_subscription_oid should also be moved to lsyscache.c. -- With Regards, Amit Kapila.
Commits
-
Move common catalog cache access routines to lsyscache.c
- 6b24d3f9cc55 16.0 landed
-
Move related functions next to each other in pg_publication.c.
- 0234ed81e958 16.0 landed
-
Allow publishing the tables of schema.
- 5a2832465fd8 15.0 cited
-
Allow GRANT on pg_log_backend_memory_contexts().
- f0b051e322d5 15.0 cited