Explicitly setting sequence next value, removes ownership of table of a serial

From: "Regina Obe" <lr(at)pcorp(dot)us>
To: <pgadmin-hackers(at)lists(dot)postgresql(dot)org>
Subject: Explicitly setting sequence next value, removes ownership of table of a serial
Date: 2023-02-09 22:47:22
Message-ID: 004c01d93cd8$7a0f8420$6e2e8c60$@pcorp.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Aditya Toshniwal 2023-02-10 04:55:26 Re: Explicitly setting sequence next value, removes ownership of table of a serial
Previous Message Akshay Joshi 2023-02-09 11:43:33 pgAdmin 4 v6.20 Released