On Mon, Sep 12, 2022 at 11:45 PM Nikita Malakhov <[email protected]> wrote:
> It would be more clear for complex data types like JSONB, where developers
> could
> need some additional functionality to work with internal representation of
> data type,
> and its full potential is revealed in our JSONB toaster extension. The JSONB
> toaster
> is still in development but we plan to make it available soon.
Okay. It'll be good to have that, because as it is now it's hard to
see the whole picture.
> On installing dummy_toaster contrib: I've just checked it by making a patch
> from commit
> and applying onto my clone of master and 2 patches provided in previous email
> without
> any errors and sll checks passed - applying with git am, configure with
> debug, cassert,
> depend and enable-tap-tests flags and run checks.
> Please advice what would cause such a behavior?
I don't think the default pg_upgrade tests will upgrade contrib
objects (there are instructions in src/bin/pg_upgrade/TESTING that
cover manual dumps, if you prefer that method). My manual steps were
roughly
=# CREATE EXTENSION dummy_toaster;
=# CREATE TABLE test (t TEXT
STORAGE external
TOASTER dummy_toaster_handler);
=# \q
$ initdb -D newdb
$ pg_ctl -D olddb stop
$ pg_upgrade -b <install path>/bin -B <install path>/bin -d
./olddb -D ./newdb
(where <install path>/bin is on the PATH, so we're using the right binaries).
Thanks,
--Jacob
