Re: pgsql: Add VACUUM/ANALYZE BUFFER_USAGE_LIMIT option - Mailing list pgsql-committers

From Kyotaro Horiguchi
Subject Re: pgsql: Add VACUUM/ANALYZE BUFFER_USAGE_LIMIT option
Date
Msg-id 20230411.102335.1643720544536884844.horikyota.ntt@gmail.com
Whole thread Raw
In response to pgsql: Add VACUUM/ANALYZE BUFFER_USAGE_LIMIT option  (David Rowley <drowley@postgresql.org>)
Responses Re: pgsql: Add VACUUM/ANALYZE BUFFER_USAGE_LIMIT option
Re: pgsql: Add VACUUM/ANALYZE BUFFER_USAGE_LIMIT option
List pgsql-committers
Hello.

> Add VACUUM/ANALYZE BUFFER_USAGE_LIMIT option

This commit added the following error message.

>         errmsg("value: \"%s\": is invalid for buffer_usage_limit",

It looks as the follows on terminal.

postgres=# vacuum (buffer_usage_limit 'x');
ERROR:  value: "x": is invalid for buffer_usage_limit

I'm not sure why the message has two colons.  [1] talks about the
message but doesn't really explain the reason for this.

[1] https://www.postgresql.org/message-id/CAApHDvqs%2BFcw9Yrn4ORCAX0xKK1-SiCC0w1j7Dhg%3DG9hrvag7g%40mail.gmail.com

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center



pgsql-committers by date:

Previous
From: Peter Geoghegan
Date:
Subject: pgsql: Clarify nbtree posting list update desc issue.
Next
From: David Rowley
Date:
Subject: Re: pgsql: Add VACUUM/ANALYZE BUFFER_USAGE_LIMIT option