Re: adding partitioned tables to publications
amit <amitlangote09@gmail.com>
From: Amit Langote <amitlangote09@gmail.com>
To: Petr Jelinek <petr@2ndquadrant.com>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Rafia Sabih <rafia.pghackers@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2020-04-03T14:25:02Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix RELCACHE_FORCE_RELEASE issue
- 12fb189bfeaf 13.0 landed
-
Allow publishing partition changes via ancestors
- 83fd4532a721 13.0 landed
-
Add logical replication support to replicate into partitioned tables
- f1ac27bfda6c 13.0 landed
-
Refactor code to look up local replication tuple
- d8653f468789 13.0 landed
-
Some refactoring of logical/worker.c
- 97ee604d9bce 13.0 landed
-
Prepare to support non-tables in publications
- c314c147c056 13.0 landed
-
Support adding partitioned tables to publication
- 17b9e7f9fe23 13.0 landed
Attachments
- v16-0001-Add-subscription-support-to-replicate-into-parti.patch (application/octet-stream) patch v16-0001
- v16-0002-Publish-partitioned-table-inserts-as-its-own.patch (application/octet-stream) patch v16-0002
On Fri, Apr 3, 2020 at 6:34 PM Amit Langote <amitlangote09@gmail.com> wrote: > I am checking test coverage at the moment and should have the patches > ready by sometime later today. Attached updated patches. I confirmed using a coverage build that all the new code in logical/worker.c due to 0002 is now covered. For some reason, coverage report for pgoutput.c doesn't say the same thing for 0003's changes, although I doubt that result. It seems strange to believe that *none* of the new code is tested. I even checked by adding debugging elog()s next to the lines that the coverage report says aren't exercised, which tell me that that's not true. Perhaps my coverage build is somehow getting messed up, so it would be nice if someone with reliable coverage builds can confirm one way or the other. I will continue to check what's wrong. I fixed a couple of bugs in 0002. One of the bugs was that the "partition map" hash table in logical/relation.c didn't really work, so logicalrep_partition_would() always create a new entry. In 0003, changed the publication parameter name to publish_via_partition_root. -- Thank you, Amit Langote EnterpriseDB: http://www.enterprisedb.com