On Wed, Jul 31, 2019 at 2:38 AM Robert Haas wrote:
>
> On Tue, Jul 2, 2019 at 9:53 PM Amit Langote wrote:
> > Thanks for the report. This seems like a bug. Documentation claims
> > that the child tables inherit column storage options from the parent
> > table. That's actually enforced in only
On Tue, Jul 2, 2019 at 9:53 PM Amit Langote wrote:
> Thanks for the report. This seems like a bug. Documentation claims
> that the child tables inherit column storage options from the parent
> table. That's actually enforced in only some cases.
I realize I'm just repeating the same argument
Hi Alvaro,
Thanks for looking at this.
On Sat, Jul 27, 2019 at 8:38 AM Alvaro Herrera wrote:
> Thanks for the patch!
>
> I'm not completely sold on back-patching this. Should we consider
> changing it in 12beta and up only, or should we just backpatch it all
> the way back to 9.4? It's going
On 2019-Jul-03, Amit Langote wrote:
> Thanks for the report. This seems like a bug. Documentation claims
> that the child tables inherit column storage options from the parent
> table. That's actually enforced in only some cases.
> To fix this, MergeAttributesIntoExisting() should check that
Thanks Amit for the fix patch,
I have applied the patch and verified the issue.
The attached partition with altered column properties shows error as below:
postgres=# alter table p attach partition p2 for values in (2);
psql: ERROR: child table "p2" has different storage option for column "b"
Hi Prabhat,
On Tue, Jul 2, 2019 at 5:12 PM Prabhat Sahu
wrote:
>
> Hi,
>
> In below testcase when I changed the staorage option for root partition,
> newly attached partition not including the changed staorage option.
> Is this an expected behavior?
Thanks for the report. This seems like a