Re: Pluggable Storage - Andres's take - Mailing list pgsql-hackers

From Dmitry Dolgov
Subject Re: Pluggable Storage - Andres's take
Date
Msg-id CA+q6zcWMHSbLkKO7eq95t15m3R1X9FCcm0kT3dGS2gGSRO9kKw@mail.gmail.com
Whole thread Raw
In response to Re: Pluggable Storage - Andres's take  (Haribabu Kommi <kommi.haribabu@gmail.com>)
Responses Re: Pluggable Storage - Andres's take
List pgsql-hackers
> On Tue, Dec 11, 2018 at 3:13 AM Andres Freund <andres@anarazel.de> wrote:
>
> Further tasks I'm not yet planning to tackle, that I'd welcome help on:
> - pg_dump support
> - pg_upgrade testing
> - I think we should consider removing HeapTuple->t_tableOid, it should
>   imo live entirely in the slot

I'm a bit confused, but what kind of pg_dump support you're talking about?
After a quick glance I don't see so far any table access specific logic there.
To check it I've created a test access method (which is a copy of heap, but
with some small differences) and pg_dump worked as expected.

As a side note, in a table description I haven't found any mention of which
access method is used for this table, probably it's useful to show that with \d+
(see the attached patch).

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Improving collation-dependent indexes in system catalogs
Next
From: Andres Freund
Date:
Subject: Re: 'infinity'::Interval should be added