Re: Bug: trailing comma syntax error in postgres_fdw fetch_attstats()

From: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
To: SATYANARAYANA NARLAPURAM <satyanarlapuram(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Bug: trailing comma syntax error in postgres_fdw fetch_attstats()
Date: 2026-04-21 10:50:59
Message-ID: CAPmGK17AJQp7_4Kr2CrqzAYds5CAvtucMjT0o5mCspz3Q+7FHQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Apr 12, 2026 at 3:40 PM Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> wrote:
> On Sun, Apr 12, 2026 at 10:45 AM SATYANARAYANA NARLAPURAM
> <satyanarlapuram(at)gmail(dot)com> wrote:
> > When importing statistics from a remote server running PostgreSQL < 17,
> > fetch_attstats() emits three NULL placeholders for the range statistics
> > columns that don't exist on older servers. The string literal included a trailing
> > comma after the last NULL, producing invalid SQL:
> >
> > SELECT ... NULL, NULL, NULL, FROM pg_catalog.pg_stats ...
> >
> > This fails ANALYZE or IMPORT STATISTICS on a foreign table backed
> > by a pre-v17 remote server with a syntax error.
>
> My bad, I will take care of this.

The patch looks good to me. I will push it if there are no objections.

Best regards,
Etsuro Fujita

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2026-04-21 10:54:47 Re: Fix bug with accessing to temporary tables of other sessions
Previous Message David Rowley 2026-04-21 10:45:10 Re: A very quick observation of dangling pointers in Postgres pathlists