Postgres Pro
Downloads
Home   >   mailing lists

Re: DropRelFileNodeBuffers API change (was Re: [BUGS] BUG #5599: Vacuum fails due to index corruption issues) - Mailing list pgsql-hackers

From Greg Stark
Subject Re: DropRelFileNodeBuffers API change (was Re: [BUGS] BUG #5599: Vacuum fails due to index corruption issues)
Date
Msg-id AANLkTinQbJWb9=seuPpBf_oBAQDq_OiZhYUC6Rn8KdAd@mail.gmail.com
Whole thread Raw
In response to Re: DropRelFileNodeBuffers API change (was Re: [BUGS] BUG #5599: Vacuum fails due to index corruption issues)  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: DropRelFileNodeBuffers API change (was Re: [BUGS] BUG #5599: Vacuum fails due to index corruption issues)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On Sun, Aug 15, 2010 at 9:48 PM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> On 15/08/10 21:58, Tom Lane wrote:
>>
>> Does anyone have an opinion whether it's likely that any third-party
>> code is calling DropRelFileNodeBuffers directly?
>
> I doubt it. External modules shouldn't be modifying relations at such a low
> level.

Really? What about an index access method?


-- 
greg

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: DropRelFileNodeBuffers API change (was Re: [BUGS] BUG #5599: Vacuum fails due to index corruption issues)
Next
From: Tom Lane
Date:
Subject: Re: Inconsistent ::bit(N) and get_bit()?