Re: Pluggable Storage - Andres's take

From: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Pluggable Storage - Andres's take
Date: 2018-12-15 19:15:12
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-hackers

> On Tue, Dec 11, 2018 at 3:13 AM Andres Freund <andres(at)anarazel(dot)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 Content-Type Size
describe_am.patch application/octet-stream 38.9 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2018-12-15 19:34:10 Re: 'infinity'::Interval should be added
Previous Message Hugh Ranalli 2018-12-15 19:05:07 Re: BUG #15548: Unaccent does not remove combining diacritical characters