Re: Partitioned tables and relfilenode
Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
From: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
To: amitlangote09@gmail.com
Cc: Langote_Amit_f8@lab.ntt.co.jp, robertmhaas@gmail.com,
m.milyutin@postgrespro.ru, pgsql-hackers@postgresql.org
Date: 2017-03-31T06:50:28Z
Lists: pgsql-hackers
At Thu, 30 Mar 2017 20:58:35 +0900, Amit Langote <amitlangote09@gmail.com> wrote in <CA+HiwqFmrJGe4eid2EaqnCjjQxrAYR5hJfzc5Cz929WA9p=A+w@mail.gmail.com> > Thanks for the review. > > On Thu, Mar 30, 2017 at 7:37 PM, Kyotaro HORIGUCHI wrote: > > At Thu, 30 Mar 2017 18:24:16 +0900, Amit Langote wrote: > >> On 2017/03/29 23:58, Robert Haas wrote: > >> > On Wed, Mar 29, 2017 at 4:21 AM, Amit Langote > >> > <Langote_Amit_f8@lab.ntt.co.jp> wrote: > >> >> Looks correct, so incorporated in the attached updated patch. Thanks. > >> > > >> > This seems like a hacky way to limit the reloptions to just OIDs. > >> > Shouldn't we instead have a new RELOPT_KIND_PARTITIONED or something > >> > like that? > >> > >> OK, I tried that in the updated patch. > > > > The name RELOPT_KIND_PARTITIONED looks somewhat odd. RELKIND for > > partitioned tables is RELKIND_PARTITIONED_TABLE, so is this > > better to be _TABLE, even if a bit longer? > > Hm, OK. Done. > > > parseRelOptions seems to return garbage pointer if no option of > > the kind is available. > > Oops, fixed that too. > > Updated patch attached. Thank you. - Applies cleanly on master (f90d23d) - Compiled without error - Code seems fine. - Documentaion seems fine.. for me. - Passes regression test. - Leaving the ALTER-on-toast.* problem is fine for me. The regression contains the tests to fail with several reloptions only for partitioned tables. Are they still required even though it is now in the same framework with other kind of reloptions? regards, -- Kyotaro Horiguchi NTT Open Source Software Center
Commits
-
Code review for c94e6942cefe7d20c5feed856e27f672734b1e2b.
- 1d5fede4a900 10.0 landed
-
Don't allocate storage for partitioned tables.
- c94e6942cefe 10.0 landed
-
Don't scan partitioned tables.
- d3cc37f1d801 10.0 landed
-
Don't uselessly rewrite, truncate, VACUUM, or ANALYZE partitioned tables.
- 3c3bb99330aa 10.0 landed