From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | yanliang lei <msdnchina(at)163(dot)com> |
Cc: | "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: in the different schema ,the sequence name is same, and a table's column definition use this sequence,so,how can I identify sequence's schema name by system view/table: |
Date: | 2025-10-01 12:38:12 |
Message-ID: | CAKFQuwbTyugCotCc5dE-5Njy3MG3ZVgDd2c_J9=fU541dnaOWA@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Wednesday, October 1, 2025, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> On Wednesday, October 1, 2025, yanliang lei <msdnchina(at)163(dot)com> wrote:
>>
>> dbversion180=# create table schema_1.test_tab_100(c1 int default
>> nextval('seq_xx_yy'));
>>
>
> Since you didn’t schema qualify the sequence name every single time a
> default value is created the sequence will be looked up anew. The stored
> expression is not associated with any specific object.
>
> This is also why there is a separate step to mark a sequence as being
> owned by a table. That establishes a dependency that this textual form is
> unable to do.
>
>
Ignore that…we do stored the parsed representation which nominally has the
schema recorded, it’s just that the text serialization it too “helpful” by
inspecting the search_path and only produces the schema prefix if it would
be necessary to resolve the reference.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | William Sescu (Suva) | 2025-10-06 09:05:43 | Little Typo on Presskit 18 |
Previous Message | David G. Johnston | 2025-10-01 12:20:34 | Re: in the different schema ,the sequence name is same, and a table's column definition use this sequence,so,how can I identify sequence's schema name by system view/table: |