Re: Toast issues with OldestXmin going backwards - Mailing list pgsql-hackers

From Pavan Deolasee
Subject Re: Toast issues with OldestXmin going backwards
Date
Msg-id CABOikdOupDfBEmh29W22CHN1d_T2hjo+xAQZhYuz_xZROfJtEQ@mail.gmail.com
Whole thread Raw
In response to Re: Toast issues with OldestXmin going backwards  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
List pgsql-hackers

On Sat, 21 Apr 2018 at 6:46 PM, Andrew Gierth <andrew@tao11.riddles.org.uk> wrote:


So I dug into this one and it looks to me like the best approach. Here's
a draft patch against 10-stable, if nobody can think of any showstoppers
then I'll do the rest of the versions and commit them.

How does this guard against the case when the same OID gets inserted in the toast table again, with matching lengths etc? Rare but seems possible, no?

I think we should look for a more complete solution how hard these bugs are to detect and fix.

Thanks,
Pavan


--
Andrew (irc:RhodiumToad)

--
 Pavan Deolasee                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-hackers by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: Toast issues with OldestXmin going backwards
Next
From: Tom Lane
Date:
Subject: Re: Memory Leaks in query_planner in postgresql 9.4 version