Re: REINDEX VERBOSE iso-8859-1 option - Mailing list pgsql-general

From Josef Šimánek
Subject Re: REINDEX VERBOSE iso-8859-1 option
Date
Msg-id CAFp7Qwpw52ffVBQ+4Twih2ghXK8GcC+t-9hMBgZQZ8R_o1tjiw@mail.gmail.com
Whole thread Raw
In response to Re: REINDEX VERBOSE iso-8859-1 option  (Josef Šimánek <josef.simanek@gmail.com>)
List pgsql-general
My patch was partially merged at https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=52dcfda48778d16683c64ca4372299a099a15b96.

Thanks to everyone involved in this discussion.

pá 13. 12. 2019 v 2:11 odesílatel Josef Šimánek <josef.simanek@gmail.com> napsal:
I was thinking about this problem and possible documentation change again and I have prepared documentation change to solve this. See attached screenshot and HTML.


This change is based on idea of Pave Stěhule, thanks a lot for that! Similar approach was used recently in https://www.postgresql.org/docs/devel/sql-dropdatabase.html.

so 16. 11. 2019 v 18:43 odesílatel Josef Šimánek <josef.simanek@gmail.com> napsal:
Ahh, I just tried to do the same with reindexdb cli tool and the actual syntax is REINDEX (VERBOSE) TABLE sales; Sorry for unnecessary question. Anyway maybe we can add this to documentation as a example. I can prepare patch for this if welcomed.

so 16. 11. 2019 v 18:40 odesílatel Josef Šimánek <josef.simanek@gmail.com> napsal:
Hello,

according to https://www.postgresql.org/docs/11/sql-reindex.html VERBOSE option is valid for REINDEX command for 11.3 PostgreSQL server. Anyway I'm getting error using VERBOSE option.

project_production=# REINDEX VERBOSE TABLE sales;
ERROR:  syntax error at or near "VERBOSE"                
LINE 1: REINDEX VERBOSE TABLE sales;                                                      
Time: 0.235 ms

I'm wondering if I'm doing anything wrong or actual documentation is wrong. Any ideas?

pgsql-general by date:

Previous
From: Steven Winfield
Date:
Subject: RE: Row locks, SKIP LOCKED, and transactions
Next
From: Julian Backes
Date:
Subject: Streaming replication fails after some time with 'incorrect resourcemanager data checksum'