Re: Re: Probable bug with CreateFakeRelcacheEntry (now with reproducible test case)

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Re: Probable bug with CreateFakeRelcacheEntry (now with reproducible test case)
Date: 2012-09-13 16:39:18
Message-ID: CA+Tgmob7+KOgNoRVuW6XWQPb_p3Aa0zY+AHYHyzO3X8cuq4saQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Sep 12, 2012 at 7:19 PM, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> This bug seems particularly troublesome because the right fix would be
> to include the relpersistence in the WAL records that need it. But that
> can't be backported (right?).

No, because if a WAL record was written at all, then by definition the
table is RELPERSISTENCE_PERMANENT. So there's probably a localized
fix.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Dimitri Fontaine 2012-09-13 16:41:19 Re: BUG #6704: ALTER EXTENSION postgis SET SCHEMA leaves dangling relations
Previous Message Dimitri Fontaine 2012-09-13 15:28:29 Re: BUG #6704: ALTER EXTENSION postgis SET SCHEMA leaves dangling relations