From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: assert pg_class.relnatts is consistent |
Date: | 2020-02-13 08:12:48 |
Message-ID: | CA+HiwqFFn=97ONGHBTxk=d_kws0w=t=RoR=YArX8p=bpSn1_gA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Feb 13, 2020 at 4:51 PM Amit Langote <amitlangote09(at)gmail(dot)com> wrote:
> On Thu, Feb 13, 2020 at 3:23 AM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> > Forking this thread for two tangential patches which I think are more
> > worthwhile than the original topic's patch.
> > https://www.postgresql.org/message-id/20200207143935.GP403%40telsasoft.com
> >
> > Is there a better place to implement assertion from 0002 ?
>
> I would think the answer to that would be related to the answer of why
> you think we need this assert in the first place?
>
> I know I have made the mistake of not updating relnatts when I added
> relispartition, etc. to pg_class, only to be bitten by it in the form
> of seemingly random errors/crashes. Is that why?
Sorry for not having read the patch properly.
> + /* Check that pg_class data is consistent now, rather than failing obscurely later */
That seems to be it.
Thanks,
Amit
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2020-02-13 08:15:02 | Re: Identifying user-created objects |
Previous Message | Justin Pryzby | 2020-02-13 08:11:45 | Re: assert pg_class.relnatts is consistent |