From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Joe Conway <mail(at)joeconway(dot)com>, John Naylor <jcnaylor(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: missing toast table for pg_policy |
Date: | 2018-07-09 12:45:26 |
Message-ID: | 94350e8f-3034-6a36-dfb1-d0ac03150680@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 15.06.18 21:15, Joe Conway wrote:
> Not surprising -- thanks for the update.
>
>> It occurred to be that we could go further and create most toast
>> tables automatically by taking advantage of the fact that the toast
>> creation function is a no-op if there are no varlena attributes. The
>> second patch (applies on top of the first) demonstrates a setup where
>> only shared and bootstrap catalogs need to have toast declarations
>> specified manually with fixed OIDs. It's possible this way is more
>> fragile, though.
>
> Hmmm, I'll have a look.
Are you going to provide a new patch soon? This commit fest item is
otherwise not moving forward.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Christophe Courtois | 2018-07-09 12:47:51 | Un peu décu : Re: Performance regression with PostgreSQL 11 and partitioning |
Previous Message | Aleksander Alekseeev | 2018-07-09 12:22:10 | Re: [GSoC] working status |