Re: Implementing foreign data wrappers and avoiding n+1 querying

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: David Gilman <davidgilman1(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Implementing foreign data wrappers and avoiding n+1 querying
Date: 2022-12-22 03:56:30
Message-ID: CAApHDvrHs+HJ5F4Nxh3A2=v4icfXEt8naVw=EF1y+JqE5Cm6Pw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, 22 Dec 2022 at 13:31, David Gilman <davidgilman1(at)gmail(dot)com> wrote:
>
> When a fdw table participates in query planning and finds itself as
> part of a join it can output a parameterized path. If chosen, Postgres
> will dutifully call the fdw over and over via IterateForeignScan to
> fetch matching tuples. Many fdw extensions do network traffic, though,
> and it would be beneficial to reduce the total number of queries done
> or network connections established.

Sounds like you might be looking for fdw_startup_cost [1].

David

[1] https://www.postgresql.org/docs/current/postgres-fdw.html

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andreas Kretschmer 2022-12-22 04:44:01 Re: pg_wal directory max size
Previous Message Yi Sun 2022-12-22 03:00:57 pg_wal directory max size