Re: Pluggable Storage - Andres's take

From: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Peter Geoghegan <pg(at)bowt(dot)ie>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Pluggable Storage - Andres's take
Date: 2019-01-12 00:35:06
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-hackers

> On Sat, Dec 15, 2018 at 8:37 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> We need to dump the table access method at dump time, otherwise we loose
> that information.

As a result of the discussion in [1] (btw, thanks for starting it), here is
proposed solution with tracking current default_table_access_method. Next I'll
tackle similar issue for psql and probably add some tests for both patches.


Attachment Content-Type Size
pg_dump_access_method.patch application/octet-stream 27.5 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Donald Dong 2019-01-12 00:39:04 Re: Unified logging system for command-line programs
Previous Message Michael Paquier 2019-01-11 23:53:12 Re: could recovery_target_timeline=latest be the default in standby mode?