Re: tablecmds.c/MergeAttributes() cleanup

From: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Alexander Lakhin <exclusion(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Subject: Re: tablecmds.c/MergeAttributes() cleanup
Date: 2024-05-03 09:32:52
Message-ID: CAExHW5tiRmNLSGnKQ2BqK+k4i54FsU_DNSQnqSvW9yEQxXNe8A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 3, 2024 at 2:47 PM Peter Eisentraut <peter(at)eisentraut(dot)org>
wrote:

> On 30.04.24 21:48, Robert Haas wrote:
> > I took a look at this patch. Currently this case crashes:
> >
> > CREATE TABLE cmdata(f1 text COMPRESSION pglz);
> > CREATE TABLE cmdata3(f1 text);
> > CREATE TABLE cminh() INHERITS (cmdata, cmdata3);
> >
> > The patch makes this succeed, but I was initially unclear why it
> > didn't make it fail with an error instead: you can argue that cmdata
> > has pglz and cmdata3 has default and those are different. It seems
> > that prior precedent goes both ways -- we treat the absence of a
> > STORAGE specification as STORAGE EXTENDED and it conflicts with an
> > explicit storage specification on some other inheritance parent - but
> > on the other hand, we treat the absence of a default as compatible
> > with any explicit default, similar to what happens here.
>
> The actual behavior here is arguably not ideal. It was the purpose of
> the other thread mentioned upthread to improve that, but that was not
> successful for the time being.
>
> > So now I think this is committable, but I can't do it now because I
> > won't be around for the next few hours in case the buildfarm blows up.
> > I can do it tomorrow, or perhaps Peter would like to handle it since
> > it seems to have been his commit that introduced the issue.
>
> I have committed it now.
>
>
Thanks Peter.

--
Best Wishes,
Ashutosh Bapat

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Guo 2024-05-03 11:47:45 Re: A problem about partitionwise join
Previous Message Adrien Nayrat 2024-05-03 09:21:19 Re: different engine for JIT