| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
| 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-07 15:58:25 |
| Message-ID: | CAH2-WzkP9wD=fYUQh+SGh+kFJc9AngsjfiUegQKvd4ZyYWk8JQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Jun 6, 2019 at 3:00 PM David Rowley
<david(dot)rowley(at)2ndquadrant(dot)com> wrote:
> You may already be aware, but another use case for such variable-width
> identifiers was with indirect indexes as discussed in [1]
Right. I went with global indexes because indirect indexes are
probably a lot more risky as a project. I'd be particularly concerned
about the complexity of VACUUM there, whereas that doesn't seem all
that bad in the case of global indexes.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-06-07 16:09:59 | Re: Table partition with primary key in 11.3 |
| Previous Message | Tom Lane | 2019-06-07 15:41:36 | Re: pg_dump include/exclude data, was: verify checksums / CREATE DATABASE |