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

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Noah Misch <noah(at)leadboat(dot)com>, Kevin Grittner <kgrittn(at)ymail(dot)com>, 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-04 23:11:07
Message-ID: 20130404231107.GN5117@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane escribió:
> Noah Misch <noah(at)leadboat(dot)com> writes:

> > A slight variation on the committed approach would be to add a "_scannable"
> > relation fork.
>
> Not very transaction-safe, I think (consider crash midway through a
> transaction that adds or removes the fork), and in any case orders of
> magnitude more expensive than looking at a pg_class field. This really
> needs to be catalog state, not filesystem state.

We could revive the pg_class_nt patch proposed a decade ago, perhaps ...

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-04-05 00:04:08 Re: patch to add \watch to psql
Previous Message Greg Jaskiewicz 2013-04-04 22:47:46 unused code in float8_to_char , formatting.c ?