-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pg_repack fails with -I Partition_Table #264
Comments
Can you provide a test case to reproduce the issue? |
-- create partitioned table with unique key create table a2(brand_id bigint not null, i bigserial, str text not null) PARTITION BY HASH (brand_id); create table a2_0 (brand_id bigint not null, i bigserial, str text not null); ALTER TABLE ONLY public.a2 ATTACH PARTITION public.a2_0 FOR VALUES WITH (modulus 30, remainder 0); -- insert few rows INSERT INTO a2(brand_id, str) -- run pg_repack -- goto log of postgres instance -- running this query with $1 and $2 ='a2' that hopefully correct:
and the postgres log looks like: thank you |
thanks |
pg_repack fails with -I Partition_Table
the ERROR of pg_repack is:
ERROR: pg_repack failed with error: SSL SYSCALL error: EOF detected
It happens in RDS dbs Postgres11.* and Postgres12.* with pg_repack1.4.4 and pg_repakc1.4.5 respectively.
When looking into the postgres log file found the following query that actually amkes the crash of ALL entire connection to the whole instance. And the query is:
SELECT t.*, coalesce(v.tablespace, t.tablespace_orig) as tablespace_dest FROM repack.tables t, (VALUES (quote_ident('$1'::text))) as v (tablespace) WHERE (relid = ANY(repack.get_table_and_inheritors('$2'::regclass))) ORDER BY t.relname, t.schemaname;
When we tried to run only this query also without pg_repack via psql and with one of our partition table(30 partitions)
we get the same ERROR!.
Actually table "repack.tables" does not include any partitioned table.
The text was updated successfully, but these errors were encountered: