On 2025/01/06 16:17, Masahiro Ikeda wrote:
On 2024-12-20 02:57, Fujii Masao wrote:
On 2024/12/05 16:48, Masahiro Ikeda wrote:
On 2024-12-05 16:23, Yugo NAGATA wrote:
- Prints a progress report as each table is clustered.
+ Prints a progress report as each table is clustered,
+
On 2024-12-20 02:57, Fujii Masao wrote:
On 2024/12/05 16:48, Masahiro Ikeda wrote:
On 2024-12-05 16:23, Yugo NAGATA wrote:
- Prints a progress report as each table is clustered.
+ Prints a progress report as each table is clustered,
+ at INFO level.
I feel like the comma could
On 2024/12/05 16:48, Masahiro Ikeda wrote:
On 2024-12-05 16:23, Yugo NAGATA wrote:
- Prints a progress report as each table is clustered.
+ Prints a progress report as each table is clustered,
+ at INFO level.
I feel like the comma could not be necessary here like the fix for
On 2024-12-05 16:23, Yugo NAGATA wrote:
- Prints a progress report as each table is clustered.
+ Prints a progress report as each table is clustered,
+ at INFO level.
I feel like the comma could not be necessary here like the fix for
the ANALYZE document, but it might be better
On Thu, 05 Dec 2024 10:39:22 +0900
Masahiro Ikeda wrote:
> On 2024-12-04 21:08, Yugo Nagata wrote:
> > This would prevent other users from make a misunderstanding as you did.
> >
> > I found the description on amvalidate also explains a message is
> > output at INFO level.
> > ( https://www.post
On 2024-12-04 21:08, Yugo Nagata wrote:
This would prevent other users from make a misunderstanding as you did.
I found the description on amvalidate also explains a message is
output at INFO level.
( https://www.postgresql.org/docs/devel/index-functions.html )
Problems should be reported wit
On Tue, 03 Dec 2024 18:23:11 +0900
Masahiro Ikeda wrote:
> Hi,
>
> I'd like to clarify the log message level of the VERBOSE option
> because I misunderstood that VACUUM VERBOSE messages cannot be
> printed in the server log.
>
> Although the hint is mentioned in "Table 19.2. Message Severity Le
