From: | walther(at)technowledgy(dot)de |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: fixing CREATEROLE |
Date: | 2022-11-22 16:04:58 |
Message-ID: | 0883f5cf-ff96-847b-127a-496efebc476f@technowledgy.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane:
> No, we don't support partial indexes on catalogs, and I don't think
> we want to change that. Partial indexes would require expression
> evaluations occurring at very inopportune times.
I see. Is that the same for indexes *on* an expression? Or would those
be ok?
With a custom operator, an EXCLUDE constraint on the ROW(reldatabase,
relname) expression could work. The operator would compare:
- (0, name1) and (0, name2) as name1 == name2
- (db1, name1) and (0, name2) as name1 == name2
- (0, name1) and (db2, name2) as name1 == name2
- (db1, name1) and (db2, name2) as db1 == db2 && name1 == name2
or just (db1 == 0 || db2 == 0 || db1 == db2) && name1 == name2.
Now, you are going to tell me that EXCLUDE constraints are not supported
on catalogs either, right? ;)
Best,
Wolfgang
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Pyhalov | 2022-11-22 16:05:29 | Re: Partial aggregates pushdown |
Previous Message | Simon Riggs | 2022-11-22 16:02:40 | Re: Code checks for App Devs, using new options for transaction behavior |