From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: Bruno Bonfils <asyd@asyd.net>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: Alexey Bashtanov <alexey@brandwatch.com>
Subject: Re: About #13489, array dimensions and CREATE TABLE ... LIKE
Date: Mon, 20 Nov 2023 21:13:01 -0500
Message-ID: <1403260.1700532781@sss.pgh.pa.us> (raw)
In-Reply-To: <ZVwQ6Fyh2SghkXja@momjian.us>
References: <ZD+14YZ4IUue8Rhi@gendo.asyd.net>
<ZPuN20z3HcBXdKow@momjian.us>
<ZVwI_ozT8z9MCnIZ@momjian.us>
<1402391.1700532261@sss.pgh.pa.us>
<ZVwQ6Fyh2SghkXja@momjian.us>
Bruce Momjian <bruce@momjian.us> writes:
> On Mon, Nov 20, 2023 at 09:04:21PM -0500, Tom Lane wrote:
>> Bruce Momjian <bruce@momjian.us> writes:
>>> An alternate approach would
>>> be to remove pg_attribute.attndims so we don't even try to preserve
>>> dimensionality.
>> I could get behind that, perhaps. It looks like we're not using the
>> field in any meaningful way, and we could simplify TupleDescInitEntry
>> and perhaps some other APIs.
> So should I work on that patch or do you want to try? I think we should
> do something.
Let's wait for some other opinions, first ...
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-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, bruce@momjian.us, asyd@asyd.net, pgsql-hackers@postgresql.org, alexey@brandwatch.com
Subject: Re: About #13489, array dimensions and CREATE TABLE ... LIKE
In-Reply-To: <1403260.1700532781@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