Re: making update/delete of inheritance trees scale better

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: making update/delete of inheritance trees scale better
Date: 2021-03-03 14:39:01
Message-ID: CA+HiwqHKomeNCFXBRfWw3qyFjeEBxtszFj3tGG6GR3q=bezMBg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Just noticed that a test added by the recent 927f453a941 fails due to
0002. We no longer allow moving a row into a postgres_fdw partition
if it is among the UPDATE's result relations, whereas previously we
would if the UPDATE on that partition is already finished.

To fix, I've adjusted the test case. Attached updated version.

--
Amit Langote
EDB: http://www.enterprisedb.com

Attachment Content-Type Size
v10-0001-Overhaul-how-updates-compute-new-tuple.patch application/octet-stream 76.7 KB
v10-0002-Revise-how-inherited-update-delete-are-handled.patch application/octet-stream 204.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2021-03-03 14:43:16 Re: "has_column_privilege()" issue with attnums and non-existent columns
Previous Message Peter Eisentraut 2021-03-03 14:33:05 Re: contrib/cube - binary input/output handlers