From: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, Robert Haas <robertmhaas(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] Pluggable storage |
Date: | 2018-04-20 06:44:25 |
Message-ID: | CAJrrPGfRGtRz_-Qyt_hK9KCQYdN=pbpjPooAHM9dZhJmqwN8fg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Mar 29, 2018 at 4:54 PM, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>
wrote:
>
> The attached patches doesn't work with recent JIT changes that are gone in
> master, because of removal many of the members from TupleTableSlot
> structure
> and it effects the JIT tuple deforming. This is yet to fixed.
>
> There is an another thread proposed by Andres in abstracting the
> TupleTableslot
> dependency from HeapTuple in [1]. Based on the output of that thread, these
> patches needs an update.
>
Here I attached a patches that are rebased to the latest master.
Apart from rebase, I have added the support for external relation to be
stored in the
pg_class. These are additional relations that may be used by the
extensions. Currently
these relations cannot be queried from SQL statements and also these
relations cannot
be dumped using pg_dump. Yet to check and confirm the pg_upgrade of these
relations.
JIT doesn't work at yet with these patches.
Regards,
Hari Babu
Fujitsu Australia
From | Date | Subject | |
---|---|---|---|
Next Message | Vladimir Sitnikov | 2018-04-20 06:45:18 | Re: Built-in connection pooling |
Previous Message | Teodor Sigaev | 2018-04-20 06:41:58 | Re: Corrupted btree index on HEAD because of covering indexes |