Re: BUG #17870: Analyze on remote postgresql_fdw table never finish

From: Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17870: Analyze on remote postgresql_fdw table never finish
Date: 2023-03-28 06:34:32
Message-ID: CAK-MWwQ+V5BTww8B3egQ1y2WTwzxsmw3pJNW3RUxV-bPUQNNkw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Mar 28, 2023 at 1:43 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> > Is it expected that the analyze of foreign table will fetch whole table
> to
> > local size (quite a task for 2TB table)?
>
> Yes. There's an improvement in the works for v16 (8ad51b5f4).
>
> regards, tom lane
>

Thank you for an explanation.
So using use_remote_estimate only way to work with huge fdw tables atm.
Is this behaviour of analyze over fdw documented somewhere?

--
Maxim Boguk
Senior Postgresql DBA
https://dataegret.com/

Phone UA: +380 99 143 0000
Phone AU: +61 45 218 5678

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Amit Regmi 2023-03-28 10:57:34 Fwd: NEED RPM FILE OF LATEST POSTGRE supported for AIX 7.2
Previous Message Maxim Boguk 2023-03-28 06:28:04 Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time