| From: | Robert Haas <robertmhaas(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: ALTER TYPE OWNER fails to recurse to multirange |
| Date: | 2024-01-15 20:01:25 |
| Message-ID: | CA+Tgmob2Ku6Mnk=4Z8iLqNXra8NmX+t9EmED5Hy+DZR+81UqUQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 15, 2024 at 2:28 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I'm reasoning by analogy to array types, which are automatically
> created and automatically updated to keep the same ownership
> etc. properties as their base type. To the extent that multirange
> types don't act exactly like that, I say it's a bug/oversight in the
> multirange patch. So I think this is a backend bug, not a pg_dump
> bug.
Oh...
Well, I guess maybe I'm just clueless. I thought that the range and
multirange were two essentially independent objects being created by
the same command. But I haven't studied the implementation so maybe
I'm completely wrong.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2024-01-15 20:17:43 | Re: Forbid the use of invalidated physical slots in streaming replication. |
| Previous Message | Robert Haas | 2024-01-15 19:52:11 | Re: gai_strerror() is not thread-safe on Windows |