Horton

Re: [PATCH] Sort policies and triggers by table name in pg_dump.

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: Benjie Gillam <benjie@jemjie.com>
Cc: pgsql-hackers@postgresql.org
Date: 2019-09-25T07:15:43Z
Lists: pgsql-hackers 
On Tue, Sep 24, 2019 at 08:48:33AM +0100, Benjie Gillam wrote:
> Here we create two identically named triggers and two identically
> named policies on tables foo and bar. If instead we ran these
> statements in a different order (or if the object IDs were to wrap)
> the order of the pg_dump would be different even though the
> databases are identical other than object IDs. The attached
> patch eliminates this difference.

Thanks.  Perhaps you could add your patch to the next commit fest
then at https://commitfest.postgresql.org/25/?

This way, your patch gains more visibility for potential reviews.
Another key thing to remember is that one patch authored requires one
other patch of equal difficulty to be reviewed.
--
Michael

Commits

  1. Stabilize pg_dump output order for similarly-named triggers and policies.