Hello,
At Tue, 28 Mar 2017 08:50:58 -0700, Jeff Janes wrote in
I accidentally sent this off-list, sending to the list now:
On Sun, Mar 26, 2017 at 10:38 PM, Kyotaro HORIGUCHI <
horiguchi.kyot...@lab.ntt.co.jp> wrote:
> At Sat, 25 Mar 2017 19:53:47 -0700, Jeff Janes
> wrote in
I'd like to have a comment from Heikki or Tom.
At Mon, 27 Mar 2017 16:49:08 +0900, Masahiko Sawada
wrote in
> On Mon, Mar 27, 2017 at 2:38 PM, Kyotaro HORIGUCHI
> wrote:
On Mon, Mar 27, 2017 at 2:38 PM, Kyotaro HORIGUCHI
wrote:
> At Sat, 25 Mar 2017 19:53:47 -0700, Jeff Janes wrote
> in
At Sat, 25 Mar 2017 19:53:47 -0700, Jeff Janes wrote in
On Thu, Mar 23, 2017 at 7:01 PM, Kyotaro HORIGUCHI <
horiguchi.kyot...@lab.ntt.co.jp> wrote:
> At Wed, 22 Mar 2017 02:15:26 +0900, Masahiko Sawada
> wrote in gmail.com>
> > On Mon, Mar 20, 2017 at 11:28 PM,
On Fri, Mar 24, 2017 at 11:01 AM, Kyotaro HORIGUCHI
wrote:
> At Wed, 22 Mar 2017 02:15:26 +0900, Masahiko Sawada
> wrote in
>> On Mon, Mar 20, 2017 at 11:28 PM, Robert
At Wed, 22 Mar 2017 02:15:26 +0900, Masahiko Sawada
wrote in
> On Mon, Mar 20, 2017 at 11:28 PM, Robert Haas wrote:
> > On Sat, Mar 18, 2017 at 5:42 PM, Jeff Janes
On Mon, Mar 20, 2017 at 11:28 PM, Robert Haas wrote:
> On Sat, Mar 18, 2017 at 5:42 PM, Jeff Janes wrote:
>> Isn't HEAP2_CLEAN only issued before an intended HOT update? (Which then
>> can't leave the block as all visible or all frozen). I think the
On Sat, Mar 18, 2017 at 5:42 PM, Jeff Janes wrote:
> Isn't HEAP2_CLEAN only issued before an intended HOT update? (Which then
> can't leave the block as all visible or all frozen). I think the issue is
> here is HEAP2_VISIBLE or HEAP2_FREEZE_PAGE. Am I reading this
On Sat, Mar 18, 2017 at 2:09 PM, Masahiko Sawada
wrote:
> On Fri, Mar 17, 2017 at 9:37 PM, Jeff Janes wrote:
> > With some intensive crash-recovery testing, I've run into a situation
> where
> > I get some bad table bloat. There will be large swaths
On Fri, Mar 17, 2017 at 9:37 PM, Jeff Janes wrote:
> With some intensive crash-recovery testing, I've run into a situation where
> I get some bad table bloat. There will be large swaths of the table which
> are empty (all results from heap_page_items other than lp are
With some intensive crash-recovery testing, I've run into a situation where
I get some bad table bloat. There will be large swaths of the table which
are empty (all results from heap_page_items other than lp are either zero
or NULL), but have zero available space in the fsm, and are marked as
13 matches
Mail list logo