Re: Partitioned tables and relfilenode
Simon Riggs <simon@2ndquadrant.com>
From: Simon Riggs <simon@2ndquadrant.com>
To: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2017-02-19T20:31:40Z
Lists: pgsql-hackers
On 16 February 2017 at 11:32, Simon Riggs <simon@2ndquadrant.com> wrote: > On 10 February 2017 at 06:19, Amit Langote > <Langote_Amit_f8@lab.ntt.co.jp> wrote: > >> the "right thing" here being that the >> command's code either throws an error or warning (in some cases) if the >> specified table is a partitioned table or ignores any partitioned tables >> when it reads the list of relations to process from pg_class. > > This is a massive assumption and deserves major discussion. > > My expectation is that "partitioned tables" are "tables". Anything > else seems to fly in the face of both the SQL Standard and the POLA > principle for users coming from other database systems. > > IMHO all the main actions should all "just work" not throw errors. This included DROP TABLE, which I commented on before. CASCADE should not be required. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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