From: | Keith Fiske <keith(dot)fiske(at)crunchydata(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | "Efrain J(dot) Berdecia" <ejberdecia(at)yahoo(dot)com>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Amit Langote <amitlangote09(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #15954: Unable to alter partitioned table to set logged |
Date: | 2019-08-22 14:37:20 |
Message-ID: | CAODZiv66MC0Tt=SyhHVEyV2gpuwRb+Oav-t0G_tvtUL4Hxaj+w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Aug 21, 2019 at 9:44 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> On Wed, Aug 21, 2019 at 09:24:38AM -0400, Keith Fiske wrote:
> > As the others have stated, I think we just need to get some sort of
> > consistent method of handling this. Currently running an ALTER TABLE on
> the
> > parent to change the UNLOGGED state simply does nothing which is not
> > intuitive whatsoever. Even if it's just throwing an error saying you
> cannot
> > change this property, that would be better until a more thorough solution
> > can be implemented in the future.
>
> One problem with an error is that it may break existing application
> code :(
> --
> Michael
>
Their application is already broken if it's expecting the property to
actually change.
--
Keith Fiske
Senior Database Engineer
Crunchy Data - http://crunchydata.com
From | Date | Subject | |
---|---|---|---|
Next Message | Thakur, Jitender | 2019-08-22 14:55:29 | PostgreSQL Not Working |
Previous Message | Kyotaro Horiguchi | 2019-08-22 08:14:39 | Re: BUG #15954: Unable to alter partitioned table to set logged |