On 1/15/26 09:06, pramod gupta wrote:
Reply to list also
Ccing list
Hi Adrian,
Thanks for you quick response, Did in the same way but its not working.
1) Show your configuration.
2) Is the client you are running the query as in the same location as
~/.pg_ai.config?
3) Does the Postgres log show anything?
Regards,
Pramod Gupta
On Thu, Jan 15, 2026 at 10:21 PM Adrian Klaver
<[email protected] <mailto:[email protected]>> wrote:
On 1/15/26 08:42, pramod gupta wrote:
> 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.
It is AI it should know the answer.
That being said.
1) Did you, in the config file, follow the format here?:
https://benodiwal.github.io/pg_ai_query/configuration.html <https://
benodiwal.github.io/pg_ai_query/configuration.html>.
2) Is the client you are running the query as in the same location as
~/.pg_ai.config?
>
> Thanks in advance.
> Pramod Gupta
>
---------------------------------------------------------------------------------------------------------------------------------------
>
> On Mon, Dec 29, 2025 at 9:23 PM pramod gupta
<[email protected] <mailto:[email protected]>
> <mailto:[email protected]
<mailto:[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
>
--
Adrian Klaver
[email protected] <mailto:[email protected]>
--
Adrian Klaver
[email protected]
