| From: | Rumpi Gravenstein <rgravens(at)gmail(dot)com> | 
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> | 
| Cc: | "Colin 't Hart" <colinthart(at)gmail(dot)com>, PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> | 
| Subject: | Re: Two sequences associated with one identity column | 
| Date: | 2025-10-30 15:22:31 | 
| Message-ID: | CAEpg1wBP7U6CiaJFz1LeH3A01jRgg6iZsyrmFk_jEHKfWgesdg@mail.gmail.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
I've seen two indexes created on the same table/column when you create a
primary key as part of table create ddl and then also run a separate create
index statement for the same table/column.
On Thu, Oct 30, 2025 at 10:42 AM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> On 10/30/25 01:55, Colin 't Hart wrote:
> >           relname          | relnamespace | relpersistence
> > --------------------------+--------------+----------------o
> >   <sequence1>  |    524799410 | p
> >   <sequence2>  |    524799410 | p
> > (2 rows)
> >
>
> Well so much for that guess. I was exploring the idea that the sequence
> may have been unlogged at some point and you had both a logged(p) and
> unlogged(u) instance of each.
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>
>
>
-- 
Rumpi Gravenstein
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitrios Apostolou | 2025-10-30 15:55:18 | Why isn't my table auto-analyzed/vacuumed? | 
| Previous Message | Adrian Klaver | 2025-10-30 14:42:26 | Re: Two sequences associated with one identity column |