Re: BUG #15954: Unable to alter partitioned table to set logged

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Keith Fiske <keith(dot)fiske(at)crunchydata(dot)com>
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-21 13:44:34
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs

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 :(

In response to


Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-08-21 13:45:13 Re: BUG #15971: Behaviour of SUBSTR function depending on its arguments
Previous Message Merlin Moncure 2019-08-21 13:39:12 Re: BUG #15967: Sequence generation using NEXTVAL() fails on 64bit systems