Re: Added schema level support for publication.
Peter Smith <smithpb2250@gmail.com>
From: Peter Smith <smithpb2250@gmail.com>
To: "houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>
Cc: Greg Nancarrow <gregn4422@gmail.com>,
Masahiko Sawada <sawada.mshk@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Amit Kapila <amit.kapila16@gmail.com>, Peter Eisentraut <peter.eisentraut@enterprisedb.com>, "tanghy.fnst@fujitsu.com" <tanghy.fnst@fujitsu.com>,
Ajin Cherian <itsajin@gmail.com>, Rahila Syed <rahilasyed90@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>,
vignesh C <vignesh21@gmail.com>
Date: 2021-09-02T22:33:49Z
Lists: pgsql-hackers
On Thu, Sep 2, 2021 at 6:50 PM houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com> wrote: > > From Wed, Sep 1, 2021 2:36 PM Peter Smith <smithpb2250@gmail.com> wrote: > > Schema objects are not part of the publication. Current only TABLES are in > > publications, so I thought that \dRp+ output would just be the of "Tables" in > > the publication. Schemas would not even be displayed at all (except in the > > table name). > > I think one use case of schema level publication is it can automatically > publish new table created in the shcema(same as ALL TABLE publication). So, > IMO, \dRp+ should output Schema level publication separately to make the user > aware of it. OK. That is a fair point. ------ Kind Regards, Peter Smith. Fujitsu Australia
Commits
-
Include schema/table publications even with exclude options in dump.
- 4aa6fa3cd0a2 18.0 landed
-
Rename some enums to use TABLE instead of REL.
- b3812d0b9bcf 15.0 landed
-
Add tap tests for the schema publications.
- 6b0f6f79eef2 15.0 landed
-
Allow publishing the tables of schema.
- 5a2832465fd8 15.0 landed
-
In pg_dump, use simplehash.h to look up dumpable objects by OID.
- 92316a4582a5 15.0 cited