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

From: Michael Lewis <mlewis(at)entrata(dot)com>
To: Eugene Pazhitnov <pazhitnov(at)gmail(dot)com>
Cc: PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_repack: WARNING: relation must have a primary key or not-null unique keys
Date: 2020-06-16 14:08:48
Message-ID: CAHOFxGqX1XKJmYnUXH5KA1up-8pk8bH9yzc5+_9Y+Kg9ZFcv6Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Jun 16, 2020, 4:52 AM Eugene Pazhitnov <pazhitnov(at)gmail(dot)com> wrote:

> xbox=> \d herostat
> Table "public.herostat"
> Indexes:
> "herostat_pkey" PRIMARY KEY, btree (xuid, titleid, heroid) INCLUDE
> (valfloat)
>
> WARNING: relation "public.herostat" must have a primary key or not-null
> unique keys
>
> What is wrong and what I can do to fix it?
>

I don't know, but I would guess that the "include" option is not supported
by pg_repack.

>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Susan Joseph 2020-06-16 14:12:04 Minor Upgrade Question
Previous Message Laurenz Albe 2020-06-16 13:49:38 Re: Something else about Redo Logs disappearing