Re: Error with index on unlogged table - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Error with index on unlogged table
Date
Msg-id CA+TgmoYGiEBm8afXa6vNESL+T4LcCK-ugF-+SFvmpLMfoB607g@mail.gmail.com
Whole thread Raw
In response to Re: Error with index on unlogged table  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Error with index on unlogged table
List pgsql-hackers
On Mon, Nov 30, 2015 at 9:53 PM, Michael Paquier
<michael.paquier@gmail.com> wrote:
>> I feel quite uncomfortable that it solves the problem from a kind
>> of nature of unlogged object by arbitrary flagging which is not
>> fully corresponds to the nature. If we can deduce the necessity
>> of fsync from some nature, it would be preferable.
>
> INIT_FORKNUM is not something only related to unlogged relations,
> indexes use them as well.

Eh, what?

Indexes use them if they are indexes on unlogged tables, but they'd
better not use them in any other situation.  Otherwise bad things are
going to happen.

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: mdnblocks() sabotages error checking in _mdfd_getseg()
Next
From: Robert Haas
Date:
Subject: Re: Error with index on unlogged table