Re: Allowing extensions to find out the OIDs of their member objects - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Allowing extensions to find out the OIDs of their member objects
Date
Msg-id 20190122190933.fnv5ws4yhbl3cisk@alap3.anarazel.de
Whole thread Raw
In response to Re: Allowing extensions to find out the OIDs of their member objects  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Allowing extensions to find out the OIDs of their member objects  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hi,

On 2019-01-21 19:41:26 -0500, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > It'd be more
> > realistic to create a new zone at UINT32_MAX - something, but that'd
> > likely still conflict in plenty installations (thanks to toast and WITH
> > OIDS tables).   I'm curious as to how to solve that, if you have a
> > sketch - less because of this, and more because I think it's not
> > unlikely that we'll encounter the need for this at some point not too
> > far away.
> 
> I have no idea how we'd move table or type OIDs, given that those are
> potentially on-disk.  (Actually ... are table OIDs really on-disk
> anywhere in user data?  Types yes, but tables?)

Not quite the same, but toast table oids are on-disk, inside toast
datums.

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Donald Dong
Date:
Subject: Install JIT headers
Next
From: Tomas Vondra
Date:
Subject: Re: [PROPOSAL] Shared Ispell dictionaries