From: | Tyler Brock <tyler(dot)brock(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Are OIDs for pg_types constant? |
Date: | 2022-04-20 15:30:51 |
Message-ID: | CACr_h8RVdQpniH7aNXMeRFB4beXM_uHw+6unxHiXQWPsbo8T5g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thank you Tom, this is exactly what I was looking for.
-Tyler
On Apr 20, 2022 at 11:23:59 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Tyler Brock <tyler(dot)brock(at)gmail(dot)com> writes:
>
> I am writing a program that behaves like a Postgres backend and can see
>
> that if I select oid from pg_type that the type old’s could be returned in
>
> the Row Description message for the field’s data type and that seems to
>
> work.
>
> However, I didn’t read anywhere that these are guaranteed to be
>
> constant/stable so I’d like to know if this is the case. For example: is
>
> the old for pg_type bool = 16 on every instance of Postgres?
>
>
> Hand-assigned OIDs (those below 10000) are stable in released versions.
> Those above 10K might vary across installations or PG versions. You
> might find it interesting to read
>
>
> https://www.postgresql.org/docs/current/system-catalog-initial-data.html#SYSTEM-CATALOG-OID-ASSIGNMENT
>
> Also does there exist any documentation decoding what the pg_type fields
>
> all mean?
>
>
> https://www.postgresql.org/docs/current/catalog-pg-type.html
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2022-04-20 15:52:12 | pgsql: Allow db.schema.table patterns, but complain about random garbag |
Previous Message | Tom Lane | 2022-04-20 15:23:59 | Re: Are OIDs for pg_types constant? |