You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It sure would be nice if pg_reorg could support multiple --table arguments. I realize that clusterdb, vacuumdb, reindexdb, and even pg_restore do not support multiple --table arguments (pg_dump being the odd man out), but this seems more like an oversight than an intentional design, per: http://archives.postgresql.org/pgsql-hackers/2010-08/msg00689.php
I might try to propose a TODO or patch for a few of those in-core utilities first, so that there is some precedent for us.
The text was updated successfully, but these errors were encountered:
Per Issue #18. SimpleStringList code borrowed from pg_dump and a
pending patch to add similar functionality to pg_restore,
clusterdb, vacuumdb, and reindexdb.
The error handling in reorg_one_table() could still be much improved,
so that an error processing a single table doesn't cause pg_reorg to
necessarily bail out and skip further tables, but I'll leave that for
another day.
It sure would be nice if pg_reorg could support multiple --table arguments. I realize that clusterdb, vacuumdb, reindexdb, and even pg_restore do not support multiple --table arguments (pg_dump being the odd man out), but this seems more like an oversight than an intentional design, per:
http://archives.postgresql.org/pgsql-hackers/2010-08/msg00689.php
I might try to propose a TODO or patch for a few of those in-core utilities first, so that there is some precedent for us.
The text was updated successfully, but these errors were encountered: