> On Mon, Mar 4, 2019 at 7:15 PM Andres Freund <and...@anarazel.de> wrote: > > The pluggable storage patchset contains exactly that... I've attached > the precursor patch (CREATE ACCESS METHOD ... TYPE TABLE), and the patch > for pg_dump support. They need a bit more cleanup, but it might be > useful information for this thread.
Didn't expect this to happen so quickly, thanks! > On 2019-03-04 13:25:40 -0500, Tom Lane wrote: > > Andres Freund <and...@anarazel.de> writes: > > > > > > But it does basically require breaking archive compatibility. I > > > personally am OK with that, but I thought it might be worth discussing. > > > > I don't recall there being huge pushback when we did that in the past, > > so I'm fine with it as long as there's an identifiable feature making > > it necessary. > > Cool. Then I guess we need to add the attached patch on top of a pg_dump support for table am. It contains changes to use NULL as a default value for owner / defn / dropStmt (exactly what we've changed back in 19455c9f56), and doesn't crash, since K_VERS is different.
0001-ArchiveEntry-null-handling.patch
Description: Binary data
