| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Anna Akenteva <a(dot)akenteva(at)postgrespro(dot)ru>, pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Change a constraint's index - ALTER TABLE ... ALTER CONSTRAINT ... USING INDEX ... |
| Date: | 2020-09-07 14:42:29 |
| Message-ID: | 20200907144229.GA29048@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-Sep-07, Laurenz Albe wrote:
> This patch would provide a more convenient way to do that.
>
> Again, I am not sure if that justifies the effort.
I have to admit I've seen cases where it'd be useful to have included
columns in primary keys.
TBH I think if we really wanted the feature of primary keys with
included columns, we'd have to add it to the PRIMARY KEY syntax rather
than having an ad-hoc ALTER TABLE ALTER CONSTRAINT USING INDEX command
to replace the index underneath. Then things like pg_dump would work
normally.
(I have an answer for the information_schema question Tom posed; I'd
like to know what's yours.)
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Naylor | 2020-09-07 15:16:28 | Re: [doc] minor wording improvement in a couple of places |
| Previous Message | Fujii Masao | 2020-09-07 14:38:07 | Re: Transactions involving multiple postgres foreign servers, take 2 |