| 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 07:51:01 |
| Message-ID: | CA+HiwqEZNGG_g2pq-+tTFhj7cqbPtbBRL6Ycgfu_F2t+-ZyWgw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
Thanks,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2020-02-13 08:10:12 | Re: assert pg_class.relnatts is consistent |
| Previous Message | Michael Paquier | 2020-02-13 07:48:21 | Re: pgsql: walreceiver uses a temporary replication slot by default |