Re: Store data in pg_toast for custom type fails (bug?)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Honza <honzap(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Store data in pg_toast for custom type fails (bug?)
Date: 2014-04-22 14:11:17
Message-ID: 27330.1398175877@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Honza <honzap(at)gmail(dot)com> writes:
> On 03/28/2014 07:02 PM, Tom Lane wrote:
>> I believe I understand what's going on here, and it's not quite as
>> exciting as it first appears. The issue is that we are failing to
>> honor the "toasting goes only one level deep" rule in the specific
>> case of arrays of composite type. So while it's definitely a nasty
>> bug, it affects only narrow use cases, and doesn't call into question
>> our whole vacuuming strategy or anything like that.

> I would like to ask if there is anything new in this bug?

Still working on it --- haven't you been following the other thread?
http://www.postgresql.org/message-id/flat/29007(dot)1396038881(at)sss(dot)pgh(dot)pa(dot)us

We should have a fix in time for the next set of minor releases, whenever
that is (probably a month or two). If you're feeling desperate for a
temporary solution, you could make use of one of the patches I already
posted, even though I now don't like those as a long-term answer.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2014-04-22 14:19:46 Re: AXLE Plans for 9.5 and 9.6
Previous Message Petr Jelinek 2014-04-22 13:55:00 shm_mq inconsistent behavior of SHM_MQ_DETACHED