Rudder

This is a new table from Rudder 8.2, so if you already had a Rudder 8.2, the table should have been created.
Does that happen after migrating from 8.1 ?

Hello François,

I have no clue at what point this occurred.
Is there a way to ensure our database schema is aligned with our Rudder server version (8.2.5) ?

It may be due to a migration problem. As a workaround, you can correct the table creation by applying by hand the SQL:

CREATE TABLE NodeLastCompliance (
  nodeId              text NOT NULL CHECK (nodeId <> '') primary key
, computationDateTime timestamp with time zone NOT NULL
, details             jsonb NOT NULL
);

Normally, Rudder ensures that by itself, but it looks that the migration part was removed somewhere in 8.2.x for that table. We are invistigating, an user doesn't have to care about SQL schema.

OK François,

I switched to postgres user, ran psql, connected to rudder database, then ran your command (it went OK).
Now, the error changed to:

ON CONFLICT (nodeId) DO UPDATE
  SET computationDateTime = excluded.computationDateTime, details = excluded.details  was aborted: ERREUR: droit refusé pour la table nodelastcompliance

Ok, I ran :

ALTER TABLE public.nodelastcompliance OWNER TO rudder;