| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Amit Langote <amitlangote09(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: ALTER tbl rewrite loses CLUSTER ON index |
| Date: | 2020-03-16 14:25:23 |
| Message-ID: | 20200316142523.GA14606@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-Mar-16, Justin Pryzby wrote:
> Also, should we call it "is_index_clustered", since otherwise it sounds alot
> like "+get_index_clustered" (without "is"), which sounds like it takes a table
> and returns which index is clustered. That might be just as useful for some of
> these callers.
Amit's proposed name seems to match lsyscache.c usual conventions better.
> Should we use your get_index_isclustered more widely ?
Yeah, in cluster(), mark_index_clustered().
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2020-03-16 14:29:32 | Re: Online checksums verification in the backend |
| Previous Message | David Steele | 2020-03-16 14:18:31 | Re: Option to dump foreign data in pg_dump |