| From: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "Alex V(dot)" <in_flight(at)pclovers(dot)ru>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>, tgl <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Table partition with primary key in 11.3 |
| Date: | 2019-06-06 22:00:28 |
| Message-ID: | CAKJS1f_cRNf=5Av5fxNYzYir7zR2yzU5Ws6zC6kz1coKx4mE6A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 7 Jun 2019 at 08:48, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> Andres has
> suggested that I work on variable-width table identifiers in nbtree
> for the benefit of pluggable storage engines, but I don't have much
> enthusiasm for the idea of doing that without delivering a clear
> benefit to users in the same release.
You may already be aware, but another use case for such variable-width
identifiers was with indirect indexes as discussed in [1]
[1] https://www.postgresql.org/message-id/20161018182843.xczrxsa2yd47pnru%40alvherre.pgsql
--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2019-06-06 22:37:58 | Re: postgres 11 issue? |
| Previous Message | Peter Geoghegan | 2019-06-06 20:48:30 | Re: Table partition with primary key in 11.3 |