Re: pg_dump partitions can lead to inconsistent state after restore - Mailing list pgsql-hackers

From David Rowley
Subject Re: pg_dump partitions can lead to inconsistent state after restore
Date
Msg-id CAKJS1f_wTEU_yvVqSr23p0SLXAii7t42D+L5H0EsTsDaap1YCw@mail.gmail.com
Whole thread Raw
In response to Re: pg_dump partitions can lead to inconsistent state after restore  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
List pgsql-hackers
On Wed, 24 Apr 2019 at 14:53, Amit Langote
<Langote_Amit_f8@lab.ntt.co.jp> wrote:
>
> On 2019/04/24 10:19, David Rowley wrote:
> > ERROR:  invalid input syntax for type integer: "One"
> > LINE 1: INSERT INTO public.listp1 VALUES ('One', 1);
> >
> > That settles the debate on the other thread...
>
> +1 to fixing this, although +0.5 to back-patching.
>
> The reason no one has complained so far of being bitten by this may be
> that, as each of one us has said at least once on the other thread, users
> are not very likely to create partitions with different column orders to
> begin with.  Maybe, that isn't a reason to leave it as is though.

Well, you could probably class most of the bugs that make their way
through feature freeze, alpha and beta as unlikely.  I don't think
that gives us an excuse to leave them as bugs.  If someone reported it
we'd most likely go and fix it then anyway, so I really don't see the
point in waiting until then.

-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Li Japin
Date:
Subject: Re: Symbol referencing errors
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: Regression test PANICs with master-standby setup on samemachine