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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Benjie Gillam <benjie(at)jemjie(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] Sort policies and triggers by table name in pg_dump.
Date: 2019-09-25 07:15:43
Message-ID: 20190925071543.GK1815@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Benjie Gillam 2019-09-25 07:36:24 Re: [PATCH] Sort policies and triggers by table name in pg_dump.
Previous Message Kyotaro Horiguchi 2019-09-25 06:55:46 Re: PATCH: standby crashed when replay block which truncated in standby but failed to truncate in master node