| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | walther(at)technowledgy(dot)de |
| 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:29:40 |
| Message-ID: | 3460446.1669134580@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
walther(at)technowledgy(dot)de writes:
>> 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?
Right, we don't support those on catalogs either.
> Now, you are going to tell me that EXCLUDE constraints are not supported
> on catalogs either, right? ;)
Nor those.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-11-22 16:35:00 | Re: Damage control for planner's get_actual_variable_endpoint() runaway |
| Previous Message | Tom Lane | 2022-11-22 16:28:02 | Re: Slow standby snapshot |