From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | richard coleman <rcoleman(dot)ascentgl(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: analyze foreign tables |
Date: | 2023-08-03 12:37:11 |
Message-ID: | 615ccd4a1de716c229cf125260896051b1989608.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers pgadmin-support pgsql-admin |
On Tue, 2023-08-01 at 09:47 -0400, richard coleman wrote:
> In PostgreSQL foreign tables are not automatically analyzed and analyze must be
> specifically called on each table. In the case of sharing tables between PostgreSQL
> clusters, there is the use_remote_estimate foreign server option.
>
> In some of our multi terabyte databases, manually running analyze on all of the
> foreign tables can take more than a day. This is per database containing the
> foreign schema. Since we have certain large schema that we have centrally located
> and share to all of our other database clusters, this really adds up.
I just saw that PostgreSQL v16 uses remote sampling for ANALYZE on foreign tables.
This is governed by the option "analyze_sampling" on the foreign table or the foreign
server, and the default value "auto" should be just what you need.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | richard coleman | 2023-08-03 13:02:45 | Re: analyze foreign tables |
Previous Message | Akshay Joshi | 2023-08-03 11:53:24 | [pgadmin-org/pgadmin4] b01a93: Added cascade option while creating an extension. ... |
From | Date | Subject | |
---|---|---|---|
Next Message | richard coleman | 2023-08-03 13:02:45 | Re: analyze foreign tables |
Previous Message | billy donald | 2023-08-03 11:23:25 | Re: pt 2 |
From | Date | Subject | |
---|---|---|---|
Next Message | richard coleman | 2023-08-03 13:02:45 | Re: analyze foreign tables |
Previous Message | Laurenz Albe | 2023-08-03 06:30:44 | Re: Anyway to index array with other columns |