Explicitly setting sequence next value, removes ownership of table of a serial - Mailing list pgadmin-hackers

From Regina Obe
Subject Explicitly setting sequence next value, removes ownership of table of a serial
Date
Msg-id 004c01d93cd8$7a0f8420$6e2e8c60$@pcorp.us
Whole thread Raw
Responses Re: Explicitly setting sequence next value, removes ownership of table of a serial  (Aditya Toshniwal <aditya.toshniwal@enterprisedb.com>)
List pgadmin-hackers
I noticed something which might be intentional, but seems odd.

If I do something like:

CREATE TABLE test(id serial, name text);

And then I use the pgAdmin UI to edit the current value of the sequence.
I notice it does this:

ALTER SEQUENCE IF EXISTS public.test_id_seq OWNED BY NONE; 
SELECT setval('public.test_id_seq', 2, true);


So then dropping the table, will not drop the sequence.

If I create a table with the generated syntax:

CREATE TABLE test(id integer GENERATED BY DEFAULT AS IDENTITY, name text);

Then go edit, it doesn't try to drop the ownership, just does this

SELECT setval('public.test_id_seq', 2, true);

Is there a reason why pgAdmin drops the ownership?

Thanks,
Regina








pgadmin-hackers by date:

Previous
From: Akshay Joshi
Date:
Subject: pgAdmin 4 v6.20 Released
Next
From: Aditya Toshniwal
Date:
Subject: Re: Explicitly setting sequence next value, removes ownership of table of a serial