From: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Asim R P <apraveen(at)pivotal(dot)io>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Ashwin Agrawal <aagrawal(at)pivotal(dot)io>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
Subject: | Re: Pluggable Storage - Andres's take |
Date: | 2019-01-15 07:02:38 |
Message-ID: | CAJrrPGc=Lp+6G7ZidFDZve50q5A=dyZt4WMg=_DtVo1JG2mYgA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Dec 11, 2018 at 1:13 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> Hi,
>
> On 2018-11-26 17:55:57 -0800, Andres Freund wrote:
> Further tasks I'm not yet planning to tackle, that I'd welcome help on:
> - pg_upgrade testing
>
I did the pg_upgrade testing from older version with some tables and views
exists, and all of them are properly transformed into new server with heap
as the default access method.
I will add the dimitry pg_dump patch and test the pg_upgrade to confirm
the proper access method is retained on the upgraded database.
> - I think we should consider removing HeapTuple->t_tableOid, it should
> imo live entirely in the slot
>
I removed the t_tableOid from HeapTuple and during testing I found some
problems with triggers, will post the patch once it is fixed.
Regards,
Haribabu Kommi
Fujitsu Australia
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2019-01-15 07:05:05 | Re: Pluggable Storage - Andres's take |
Previous Message | Masahiko Sawada | 2019-01-15 06:59:15 | Re: [HACKERS] Block level parallel vacuum |