From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Initializing initFileRelationIds list via write is unsafe |
Date: | 2015-06-08 16:01:02 |
Message-ID: | CA+TgmoaYUBsq_AHapow2HhqjQFXbAO2SpLCLMm=b5+SfLBb2pA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Jun 6, 2015 at 11:51 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> This suggests that CLOBBER_CACHE_ALWAYS is actually missing a pretty
> large part of the cache behavioral space. Maybe we should devise some
> sort of "CLOBBER_CACHE_RANDOMLY" option that would inject cache flush
> events more selectively, perhaps only once every thousand opportunities
> or so. And perhaps not only full cache reset events, though I confess
> to not being sure what that ought to look like.
It should probably be done pseudo-randomly, but otherwise, +1.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Claudio Freire | 2015-06-08 16:03:56 | Re: [CORE] Restore-reliability mode |
Previous Message | Robert Haas | 2015-06-08 15:59:23 | Re: Re: [COMMITTERS] pgsql: Map basebackup tablespaces using a tablespace_map file |