Andrew Dunstan wrote:
Well, yes, it's some of it, and in theory Tom's late addition of a queue
that gets all the dependencies of a table as soon as the table data is
restored should make that work better. But of course, that's not the
only time indexes are created, and each index creation command will be
doing its own heap processing, albeit that synchronised scanning will
make that lots cheaper.
As I said originally, it was just an idle thought that came to me today.
Sounds to me like another reason to separate index definition from
creation. If an index can be defined but not yet created or valid, then
you could imagine syntax like:
DEFINE INDEX blahblah1 ON mytable (some fields);
DEFINE INDEX blahblah2 ON mytable (some other fields);
[RE]INDEX TABLE mytable;
...provided that REINDEX TABLE could recreate all indexes simultaneously
as you suggest.
-Glen
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
