From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | walteniobessa(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15601: ERRO TYPE SERIAL |
Date: | 2019-01-21 23:13:19 |
Message-ID: | CAMkU=1x-wc0w6C7JDxXxmC_Lnnjt2XpP+WAqBpTu2JGg2awu2w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, Jan 21, 2019 at 4:26 PM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 15601
> Logged by: Waltênio de Bessa Mendes
> Email address: walteniobessa(at)gmail(dot)com
> PostgreSQL version: 11.1
> Operating system: Win 10
> Description:
>
> ALTER TABLE documento ALTER COLUMN id_doc TYPE SERIAL;
>
> ERROR: type "serial" does not exist
> ********** Error **********
>
> ERROR: type "serial" does not exist
> SQL state: 42704
>
>
This isn't a bug.
According to the doc (
https://www.postgresql.org/docs/current/datatype-numeric.html#DATATYPE-SERIAL
):
The data types smallserial, serial and bigserial are not true types, but
merely a notational convenience for creating unique identifier columns
(similar to the AUTO_INCREMENT property supported by some other databases)
Further down, it tells you how to turn an existing column into that behaves
just as if you had created it with 'serial' in the first place.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Waltênio de Bessa Mendes | 2019-01-21 23:29:08 | Re: BUG #15601: ERRO TYPE SERIAL |
Previous Message | Thomas Munro | 2019-01-21 21:24:10 | Re: BUG #15585: infinite DynamicSharedMemoryControlLock waiting in parallel query |