On Wed, Sep 14, 2011 at 10:58 PM, Tom Lane wrote:
> Yeah, that's about what it would take, but what I'm asking is why
> bother. The *only* case that we support here is turning a just-created,
> not-fooled-with table into a view, and I don't feel a need to promise
> that we will handle other cases
Robert Haas writes:
> I spent some more time looking at this tonight. I am wondering if
> perhaps we should just get rid of relhasindex.
-1, there is absolutely no reason to believe that's a good idea.
> ... I think we could fix Thom's complaint by changing
> DefineQueryRewrite() to call Relati
On Tue, Sep 13, 2011 at 4:31 PM, Tom Lane wrote:
> Robert Haas writes:
>> On Sep 10, 2011, at 11:26 PM, Tom Lane wrote:
>>> (IOW, rather than "fix" this I'd prefer to rip out the code altogether.
>>> But maybe we should wait a couple more years for that.)
>
>> IIRC, it's not dead code. I think y
Robert Haas writes:
> On Sep 10, 2011, at 11:26 PM, Tom Lane wrote:
>> (IOW, rather than "fix" this I'd prefer to rip out the code altogether.
>> But maybe we should wait a couple more years for that.)
> IIRC, it's not dead code. I think you can still generate such a dump if you
> use CREATE OR
On Sep 10, 2011, at 11:26 PM, Tom Lane wrote:
> Thom Brown writes:
>> I don't use rules, but in a bit of experimentation on Git master, I
>> discovered the following behaviour:
>
>> CREATE TABLE test1 (id serial primary key, things text);
>> CREATE TABLE test2 (id serial primary key, things text
Thom Brown writes:
> I don't use rules, but in a bit of experimentation on Git master, I
> discovered the following behaviour:
> CREATE TABLE test1 (id serial primary key, things text);
> CREATE TABLE test2 (id serial primary key, things text);
> ALTER TABLE test1 DROP CONSTRAINT test1_pkey;
> AL
Hi,
I don't use rules, but in a bit of experimentation on Git master, I
discovered the following behaviour:
CREATE TABLE test1 (id serial primary key, things text);
CREATE TABLE test2 (id serial primary key, things text);
ALTER TABLE test1 DROP CONSTRAINT test1_pkey;
ALTER TABLE test2 DROP CONSTR
