Re: matview scannability rehash (was Re: Drastic performance loss in assert-enabled build in HEAD)

From: Noah Misch <noah(at)leadboat(dot)com>
To: Kevin Grittner <kgrittn(at)ymail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: matview scannability rehash (was Re: Drastic performance loss in assert-enabled build in HEAD)
Date: 2013-04-05 14:27:19
Message-ID: 20130405142719.GA8155@tornado.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 05, 2013 at 07:00:38AM -0700, Kevin Grittner wrote:
> Noah Misch <noah(at)leadboat(dot)com> wrote:
>
> > The SQL commands I cited as responsible for creating or removing
> > the fork all make a new relfilenode anyway.  Thus, "add" actually
> > means creating the fork with the new relfilenode, and "remove"
> > actually means omitting the fork from the new relfilenode.  The
> > association between relfilenodes and relations is, of course,
> > transactional.
>
> The same argument applies to the currently-committed code.

True.

--
Noah Misch
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2013-04-05 14:55:17 Re: matview scannability rehash (was Re: Drastic performance loss in assert-enabled build in HEAD)
Previous Message Kevin Grittner 2013-04-05 14:00:38 Re: matview scannability rehash (was Re: Drastic performance loss in assert-enabled build in HEAD)