Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upthe parent table size is not reduced when I type '\d+' after migration #205
Comments
That's quite normal until you vacuum the parent table (of course you can do that in progress, while partitioning bgw is still running).
This is definitely not normal; table should always be accessible with all its rows. Examining server logs might help.
No, worker deletes moved data itself. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem description
Is this the correct result? should I ‘TRUNCATE parent_table’?
Environment
extname | extowner | extnamespace | extrelocatable | extversion | extconfig | extcondition
------------+----------+--------------+----------------+------------+-------------------+--------------
plpgsql | 10 | 11 | f | 1.0 | |
pg_pathman | 1030850 | 2200 | f | 1.5 | {1031004,1031015} | {"",""}
PostgreSQL 11.4 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (EulerOS 4.8.5-4), 64-bit