Re: Redesigning parallel dump/restore's wait-for-workers logic - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: Redesigning parallel dump/restore's wait-for-workers logic
Date
Msg-id CACjxUsNiB1LxfF9f4e6egjKhgpb7+7GjPxZiDapM=x6+Y41DwA@mail.gmail.com
Whole thread Raw
In response to Re: Redesigning parallel dump/restore's wait-for-workers logic  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Redesigning parallel dump/restore's wait-for-workers logic  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
This patch applies with a few minor offsets, compiles without
warning, and passes all regression tests including `make
check-world` with TAP tests enabled.  This and the related patch
dealing with the parallel API definitely make things cleaner and
easier to follow.

I find it disappointing that ACLs continue to be held  back as a
fourth step outside the framework of the "normal" ordering.  That
is an ugly hack, which makes it impossible to, for example, create
a fifth step to create indexes on materialized views and refresh
them in anything resembling a clean fashion.  Would it make sense
to deal with the ACL ordering hack in one of these patches, or
should that be left for later?

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Stas Kelvich
Date:
Subject: assert violation in logical messages serialization
Next
From: David Steele
Date:
Subject: Re: Password identifiers, protocol aging and SCRAM protocol