Re: postgres_fdw: Emit message when batch_size is reduced

From: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: solai v <solai(dot)cdac(at)gmail(dot)com>, Rafia Sabih <rafia(dot)pghackers(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, nurlan(dot)tulemisov(at)gmail(dot)com
Subject: Re: postgres_fdw: Emit message when batch_size is reduced
Date: 2026-10-15 14:08:38
Message-ID: CADkLM=ch5Vt1Ms0HeftxT7HZ1HHRPFo2pajBKYap8Htpe+2YHg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 15, 2026 at 9:55 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> On Wed, Oct 14, 2026 at 12:22 PM Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
> wrote:
> > My interest in the DEBUG messages was giving a curious user an answer to
> the question "If I'm not getting the batch_size I asked for, what
> batch_size am I actually getting?", but that should infer-able from logs
> looking for "FETCH <number> FROM cursor_name", albeit with some additional
> effort to line up which FETCH commands correspond to which FDW queries, and
> cross referencing that against the fetch_size that they've set, so it may
> be that a curious user already has the instrumentation they need.
>
> Unless I'm confused, that's fetch_size, and this patch is about
> batch_size. So, you're doing a bulk-insert to a foreign table, and the
> question is about how many separate INSERT statements we're going to
> have to issue in order to handle all the rows.
>

Yes, sorry for the confusion.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Aidar Imamov 2026-10-15 14:16:01 Re: Disable startup progress timeout during standby WAL replay
Previous Message Robert Haas 2026-10-15 13:55:42 Re: postgres_fdw: Emit message when batch_size is reduced