Re: matview niceties: pick any two of these three

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: matview niceties: pick any two of these three
Date: 2013-05-04 22:41:27
Message-ID: 1367707287.81511.YahooMailNeo@web162901.mail.bf1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Kevin Grittner <kgrittn(at)ymail(dot)com> writes:

>> What do you see that I'm missing?
>
> TBH, if I had 20-20 foresight, we'd not be having this
> discussion: either I could see that you're right and this patch
> isn't going to cause us enormous pain, or I could put my finger
> on exactly where and why it's going to hurt us.  But I can't do
> the latter today.  Nonetheless, this patch terrifies me.  It's
> ugly, it's a serious layering violation, and it flies in the face
> of very-long-standing assumptions about the semantics of heap
> storage.  My gut tells me that we *will* regret shipping things
> this way.  Nor am I impressed with the amount of functionality
> we're gaining by taking such a risk.

OK, I think there are more votes for removing unlogged matviews for
9.3 than for any other option, and it's time to make a call; so I'm
conceding the point.  Do you want me to take a shot at undoing that
and straightening things out, or given the short time and your
superior grasp of the layer boundaries, would you prefer to take
it?

--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2013-05-04 22:41:29 Re: Commit subject line
Previous Message Dimitri Fontaine 2013-05-04 20:57:44 Re: erroneous restore into pg_catalog schema