Re: pg_repack: WARNING: relation must have a primary key or not-null unique keys - Mailing list pgsql-general

From Tom Lane
Subject Re: pg_repack: WARNING: relation must have a primary key or not-null unique keys
Date
Msg-id 1301065.1592316738@sss.pgh.pa.us
Whole thread Raw
In response to pg_repack: WARNING: relation must have a primary key or not-nullunique keys  (Eugene Pazhitnov <pazhitnov@gmail.com>)
Responses Re: pg_repack: WARNING: relation must have a primary key or not-nullunique keys  (Eugene Pazhitnov <pazhitnov@gmail.com>)
List pgsql-general
Eugene Pazhitnov <pazhitnov@gmail.com> writes:
> xbox=> \d herostat
> ...
>     "herostat_pkey" PRIMARY KEY, btree (xuid, titleid, heroid) INCLUDE (valfloat)

> eugene@dignus:/var/www/html/health$ sudo -u postgres pg_repack -t herostat
> -N -d xbox
> INFO: Dry run enabled, not executing repack
> WARNING: relation "public.herostat" must have a primary key or not-null
> unique keys

Apparently pg_repack can't work with a primary key index that has INCLUDE
columns.  I have no idea whether that's a fundamental limitation or it's
just that pg_repack hasn't been taught about the INCLUDE feature.  In
either case, you need to go consult pg_repack's author(s), who may or
may not keep up on this list.

            regards, tom lane



pgsql-general by date:

Previous
From: Susan Joseph
Date:
Subject: Minor Upgrade Question
Next
From: Pepe TD Vo
Date:
Subject: create batch script to import into postgres tables