Our issue is that it takes 20hrs to index the full table. Hopefully we can add
FK in multiple child partitions concurrently, otherwise doing it per partition
offers no advantage from performance pov.
Need to test. Hopefully PG should not lock the referred table during the first
build, stopping c
On 10/19/22 08:31, Ravi Krishna wrote:
AWS Aurora based on PG 13.
Large partitioned table of 5+ billion rows and 7TB in size.
ALTER TABLE abc ADD CONSTRAINT fk_123 FOREIGN KEY (a,b,c) REFERENCES
xyz(1,2,3);
It seems this is not parallelized. Is there a way. Or directly going into
each part
AWS Aurora based on PG 13.
Large partitioned table of 5+ billion rows and 7TB in size.
ALTER TABLE abc ADD CONSTRAINT fk_123 FOREIGN KEY (a,b,c) REFERENCES xyz(1,2,3);
It seems this is not parallelized. Is there a way. Or directly going into each
partition is the only way ( not even sure it is po
