Re: pgsql: Add VACUUM/ANALYZE BUFFER_USAGE_LIMIT option

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: drowley(at)postgresql(dot)org
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Add VACUUM/ANALYZE BUFFER_USAGE_LIMIT option
Date: 2023-04-11 01:23:35
Message-ID: 20230411.102335.1643720544536884844.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message David Rowley 2023-04-11 01:59:36 Re: pgsql: Add VACUUM/ANALYZE BUFFER_USAGE_LIMIT option
Previous Message Peter Geoghegan 2023-04-11 00:55:54 pgsql: Clarify nbtree posting list update desc issue.