| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Keith Fiske <keith(dot)fiske(at)crunchydata(dot)com> |
| Cc: | Jorge Torralba <jorge(dot)torralba(at)gmail(dot)com>, legrand_legrand(at)hotmail(dot)com, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Is there a work around for partition key needed for constraint |
| Date: | 2018-10-25 13:59:31 |
| Message-ID: | 20181025135931.jbo5gnfyd5aliwhu@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On 2018-Oct-24, Keith Fiske wrote:
> The real solution will have to wait on a global index in a future version.
Actually, there might be another way to implement it, namely to use the
speculative tokens on every affected local btree, then do the actual
insert in the correct index, then remove the unused speculative tokens
from all the other indexes. Then you don't need a global tree at all.
I'm not planning to work on this, and haven't heard that anyone is.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ghiurea, Isabella | 2018-10-25 14:53:35 | upgrade slave in streaming replication from PG 10.4 to 10.5.1 |
| Previous Message | Mihalidesová Jana | 2018-10-25 09:31:35 | Using pg_basebackup via pgpool fail |