public inbox for [email protected]
help / color / mirror / Atom feedFrom: pramod gupta <[email protected]>
To: [email protected]
Subject: Re: How did VACUUM ANALYZE reclaim large TOAST bloat at disk level in PostgreSQL 16?
Date: Thu, 15 Jan 2026 22:12:36 +0530
Message-ID: <CAMxxg=YHe5vXM4hO9GWbSa-C8+HwFNYV+ABpcg336OwsZVvHkg@mail.gmail.com> (raw)
In-Reply-To: <CAMxxg=a0PCvrSenxkTSjTsBygh5KJ-bqOo2ZqJvGcsjdiECOWg@mail.gmail.com>
References: <CAMxxg=a0PCvrSenxkTSjTsBygh5KJ-bqOo2ZqJvGcsjdiECOWg@mail.gmail.com>
Hello Everyone,
I am encountering the following error while using the *pg_ai_query*
extension.
*test=# SELECT generate_query('show recent orders', null, 'gemini');ERROR:
Query generation failed: No API key available for gemini provider. Please
provide API key as parameter or configure it in
~/.pg_ai.config.test=#test=# SELECT generate_query('show recent orders',
null, 'google_ai_studio');ERROR: Query generation failed: API key
required. Pass as parameter or set OpenAI, Anthropic, or Gemini API key in
~/.pg_ai.config.test=#*
have verified all required permissions and confirmed that the
configuration is correctly placed; however, I continue to receive the above
error when using the *pg_ai.config* file.
If I execute the query by explicitly passing the API key, it works as
expected:
*select generate_query('I want to count the rows in orders
tables','MYAPIKEY','gemini');*
This works perfectly. I would appreciate guidance on how to configure this
so that the API key does not need to be passed explicitly in the query.
Please let me know if there is any alternative configuration or recommended
approach to achieve this.
Thanks in advance.
Pramod Gupta
---------------------------------------------------------------------------------------------------------------------------------------
On Mon, Dec 29, 2025 at 9:23 PM pramod gupta <[email protected]>
wrote:
> Hello Everyone,
>
> We have a table with a total size of ~628 GB, out of which ~601 GB was
> TOAST data.
> After running VACUUM ANALYZE on a weekly basis, the table size reduced
> significantly to ~109 GB, indicating a large amount of bloat removal.
>
> I would like to understand:
>
> How was VACUUM ANALYZE able to reclaim such a large amount of space,
> especially for TOAST data?
>
> Under what conditions does PostgreSQL reclaim disk space without requiring
> VACUUM FULL or CLUSTER?
>
> Is this behavior expected in PostgreSQL 16, particularly for heavily
> updated or deleted TOASTed columns?
>
> Any insights or documentation references would be greatly appreciated.
>
> PostgreSQL version: 16
>
> Thanks in advance.
> Pramod Gupta
>
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: How did VACUUM ANALYZE reclaim large TOAST bloat at disk level in PostgreSQL 16?
In-Reply-To: <CAMxxg=YHe5vXM4hO9GWbSa-C8+HwFNYV+ABpcg336OwsZVvHkg@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox