Re: About #13489, array dimensions and CREATE TABLE ... LIKE

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Bruno Bonfils <asyd(at)asyd(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Alexey Bashtanov <alexey(at)brandwatch(dot)com>
Subject: Re: About #13489, array dimensions and CREATE TABLE ... LIKE
Date: 2023-11-21 02:13:01
Message-ID: 1403260.1700532781@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Mon, Nov 20, 2023 at 09:04:21PM -0500, Tom Lane wrote:
>> Bruce Momjian <bruce(at)momjian(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message vignesh C 2023-11-21 05:28:05 Re: BUG #18203: Logical Replication initial sync failure
Previous Message Bruce Momjian 2023-11-21 02:07:36 Re: About #13489, array dimensions and CREATE TABLE ... LIKE

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2023-11-21 02:52:32 Re: Optimizing nbtree ScalarArrayOp execution, allowing multi-column ordered scans, skip scan
Previous Message Jeff Davis 2023-11-21 02:12:47 simplehash: SH_OPTIMIZE_REPEAT for optimizing repeated lookups of the same key