Re: Assign TupleTableSlot->tts_tableOid duplicated in tale AM. - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Assign TupleTableSlot->tts_tableOid duplicated in tale AM.
Date
Msg-id CAH2-WznV1iVxW7+TKNKBpqRPVy-XwKu-XmT7dZ5sO7rARFFJgg@mail.gmail.com
Whole thread Raw
In response to Assign TupleTableSlot->tts_tableOid duplicated in tale AM.  (Wenchao Zhang <zwcpostgres@gmail.com>)
Responses Re: Assign TupleTableSlot->tts_tableOid duplicated in tale AM.
List pgsql-hackers
On Tue, Sep 20, 2022 at 11:51 PM Wenchao Zhang <zwcpostgres@gmail.com> wrote:
> We can get the two assigned values are same by reading codes. Maybe we should remove one?
>
> What's more, we find that maybe we assign slot->tts_tableOid in outer interface like table_scan_getnextslot may be
betterand more friendly when we import other pluggable storage formats.
 

I suppose that you're right; it really should happen in exactly one
place, based on some overarching theory about how tts_tableOid works
with the table AM interface. I just don't know what that theory is.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: meson vs mingw, plpython, readline and other fun
Next
From: Andres Freund
Date:
Subject: Re: Strip -mmacosx-version-min options from plperl build