Re: [PG19][PATCH] Make postgres_fdw statistics import atomic - Mailing list pgsql-hackers

From Nikolay Samokhvalov
Subject Re: [PG19][PATCH] Make postgres_fdw statistics import atomic
Date
Msg-id CAM527d9ojid26mgTCnCFcm_rcAJzXZi=PUbhdBjwMEVZTS1UXA@mail.gmail.com
Whole thread
In response to Re: [PG19][PATCH] Make postgres_fdw statistics import atomic  (Etsuro Fujita <etsuro.fujita@gmail.com>)
Responses Re: [PG19][PATCH] Make postgres_fdw statistics import atomic
List pgsql-hackers
On Thu, Sep 17, 2026, Etsuro Fujita <etsuro.fujita@gmail.com> wrote:
> * You imported remote stats without re-analyzing the remote table
> after the delete operation, but that isn't supported, as noted in the
> documentation; "When using this option, it is the user's
> responsibility to ensure that the existing statistics for the remote
> table are up-to-date."

Thanks Etsuro. Agreed, my reproducer violates that requirement.
I haven't reproduced this with matching types and current remote
stats, so I'll withdraw the patch for now.

Attribute stats can still affect join estimates when reltuples=0;
I tested that. But that doesn't show this needs fixing.

Nik



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: 64-bit MultiXactOffset vs. 9.3->9.4 upgrade, pg_resetwal, "wraparound" msg
Next
From: Peter Eisentraut
Date:
Subject: Re: [PATCH] pg_dump: Restore extension config table data before user objects during pg_upgrade