On Sat, Jun 5, 2021 at 7:02 PM vignesh C <vignesh21@gmail.com> wrote: > Thanks for identifying and reporting this issue. I have \dn with the > equivalent query to display only the publication name. The updated > patch has the fix for the same.
Currently, FOR ALL TABLES is there to add all the tables(existing and future) in the current database in which the publication is created. I wonder before providing FOR SCHEMA capability, we better target FOR DATABASE first, something like CREATE PUBLICATION ... FOR DATABASE foo, bar, baz, qux; Of course users with the proper permissions on the specified databases can add them to the publication. This can help to add all the tables in other databases as well. Then, the CREATE PUBLICATION ... FOR SCHEMA foo, bar, baz, qux; makes more sense. Because, my understanding is that: database is a collection of tables, schema is a collection of databases. I may be wrong here, but it's just a thought. What do you think?
Please ignore above comment. I was confused about what a database and schema is in postgres. I'm sorry for the noise.