From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | enable_material patch |
Date: | 2010-04-18 03:23:28 |
Message-ID: | i2h603c8f071004172023m38e77b99wafb41872df8d401e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Here's a patch to add enable_material, per previous discussion. I
still think we should add enable_joinremoval also, but there wasn't a
clear consensus for that.
I'd appreciate it if someone could check this over for sanity - like,
did I get all the places where materialize nodes can be created? and,
did i prevent them from being inserted anywhere that they are
necessary for correctness?
Thanks,
...Robert
Attachment | Content-Type | Size |
---|---|---|
enable-material.patch | application/octet-stream | 5.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Kupershmidt | 2010-04-18 03:53:01 | patch: Distinguish between unique indexes and unique constraints |
Previous Message | Robert Haas | 2010-04-17 22:52:35 | Re: master in standby mode croaks |