| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | mariakatosvich <loveneet(dot)singh(at)redblink(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: REINDEX backend filtering |
| Date: | 2021-02-24 16:58:36 |
| Message-ID: | CAOBaU_bU7c_NmrXjCpXa+WdY=pgtrVNqy5EzvZeYL20naib2kQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Thu, Feb 25, 2021 at 12:11 AM mariakatosvich
<loveneet(dot)singh(at)redblink(dot)com> wrote:
>
> From what I heard on this topic, the goal is to reduce
> the amount of time necessary to reindex a system so as REINDEX only
> works on indexes whose dependent collation versions are not known or
> works on indexes in need of a collation refresh (like a reindexdb
> --all --collation -j $jobs).
That's indeed the goal. The current patch only adds infrastructure
for the REINDEX command, which will make easy to add the option for
reindexdb. I'll add the reindexdb part too in the next version of the
patch.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexandre Arruda | 2021-02-24 16:59:39 | Re: [Proposal] Global temporary tables |
| Previous Message | Alvaro Herrera | 2021-02-24 16:47:49 | Re: Bizarre behavior of \w in a regular expression bracket construct |