Re: order of pg_dump command "create sequence"
| От | Ron Johnson |
|---|---|
| Тема | Re: order of pg_dump command "create sequence" |
| Дата | |
| Msg-id | CANzqJaB+nyci9jK-ttnT=0rjhGotCzb-6fpoGKufzSxCimTC9A@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: order of pg_dump command "create sequence" ("David G. Johnston" <david.g.johnston@gmail.com>) |
| Список | pgsql-admin |
On Fri, Jun 6, 2025 at 9:54 AM David G. Johnston <david.g.johnston@gmail.com> wrote:
On Friday, June 6, 2025, Антон Глушаков <a.glushakov86@gmail.com> wrote:/* create a function that will move the sequence */CREATE FUNCTION public.gen_id() RETURNS character varying
LANGUAGE sql IMMUTABLE AS
$$
SELECT 'PREFIX_'||nextval('public.my_seq'::regclass)::VARCHAR;
$$;Stating immutable is a lie and the breakage is on your head for violating using only immutable functions in generated expressions.
It's too bad that the server, when it sees the CREATE FUNCTION DDL, can't notice the obvious (to humans) not-immutable nature of the function and throw a warning. It would certainly be hideously complex code, though, and miss lots of cases while throwing some false positive messages.
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
В списке pgsql-admin по дате отправления: