On 2018-May-17, Tom Lane wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
> > Yeah, but I'm not sure I like that solution very much. I don't think
> > abusing the tableoid to store a remote table OID is very nice.
>
> I'd say it's totally unacceptable. Tableoid *has to* be something
> that you can look up in the local pg_class instance, or serious
> confusion will ensue.
Can we just add a new junk attr, with its own fixed system column
number? I think that's what Robert was proposing.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services