From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: Álvaro Herrera <alvherre@kurilemu.de>
Cc: jian he <jian.universality@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: Kirill Reshke <reshkekirill@gmail.com>
Subject: Re: misleading error message in ProcessUtilitySlow T_CreateStatsStmt
Date: Fri, 12 Sep 2025 09:49:44 -0400
Message-ID: <2107323.1757684984@sss.pgh.pa.us> (raw)
In-Reply-To: <78fdbf09-ec9a-498f-91bd-392fc486117b@eisentraut.org>
References: <202508291248.qnqtditzyqm2@alvherre.pgsql>
<74fab830-7a87-4a9e-824d-f28a1baf11ca@eisentraut.org>
<78fdbf09-ec9a-498f-91bd-392fc486117b@eisentraut.org>
Peter Eisentraut <peter@eisentraut.org> writes:
> I propose the attached patch to fix this. I think this restores the
> original meaning better.
I'm okay with this wording change, but I would stay with
ERRCODE_FEATURE_NOT_SUPPORTED rather than calling this
a "syntax error". It's not a syntax error IMV, but a
potential feature that we have deliberately left syntax
space for, even though we don't yet have ideas about
a workable implementation.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, peter@eisentraut.org, alvherre@kurilemu.de, jian.universality@gmail.com, reshkekirill@gmail.com
Subject: Re: misleading error message in ProcessUtilitySlow T_CreateStatsStmt
In-Reply-To: <2107323.1757684984@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox