QGIS » QGIS Application

Same issue with last nightly. I've attached the SQL code. For example table 'choix_secteur_activite' has the good behavior and 'choix_public_cible' doesn't.

I am experiencing the exact same behaviour as described by the original poster. Today for the first time I ran into an issue where the PostgreSQL sequence was not providing the nextval('name_of_sequence'::regclass) in the edit form. When comparing against other tables in the database, others preform normally.

Digging a little deeper through the layer properties I also saw that the working table showed my gid SERIAL PRIMARY KEY column as 'Text Edit' widget Type, whereas the non-working table showed it as 'Range' as described by the original poster.

At the database level both these tables were created with the exact same process. Here is the SQL for comparison.
CREATE TABLE "temp_BC_ParcelMap_Knockout_20170727_a"
(
gid serial NOT NULL,
grmn_type character varying,
the_geom geometry(Geometry,4326),
CONSTRAINT "temp_BC_ParcelMap_Knockout_20170727_a_pkey" PRIMARY KEY (gid)
)
WITH (
OIDS=TRUE
);
ALTER TABLE "temp_BC_ParcelMap_Knockout_20170727_a"
OWNER TO postgres;

CREATE TABLE "temp_BC_ParcelMap_Knockout_20190319_a"
(
gid serial NOT NULL,
grmn_type character varying,
the_geom geometry(Geometry,4326),
CONSTRAINT "temp_BC_ParcelMap_Knockout_20190319_a_pkey" PRIMARY KEY (gid)
)
WITH (
OIDS=TRUE
);
ALTER TABLE "temp_BC_ParcelMap_Knockout_20190319_a"
OWNER TO postgres;

It seems all the new tables I create are affected by this behaviour, but older tables which have been within the database for the past few years work as expected. Was there any solution to this issue?

I've tested these tables in QGIS 3.6.0 and QGIS 2.18.21 and the bug is affecting both. Our database server is running PostgreSQL 9.4.19 on Debian 8.11.

Thanks David for your feedback. We used trigger to increment sequence as a workaround.