Christian Barthel writes:
> On Thursday, July 21, 2022, Adrian Klaver wrote:
>> Why does it matter?
> As the comment in pg_dump.c states, logically identical schemas should
> produce identical dumps:
Agreed, but this is far from the only deficiency in DOTypeNameCompare.
If we're going to try to
On 7/21/22 10:59, Christian Barthel wrote:
On Thursday, July 21, 2022, Adrian Klaver wrote:
Why does it matter?
As the comment in pg_dump.c states, logically identical schemas should
produce identical dumps:
| * We rely on dependency information to help us determine a safe order,
| so * the
On Thursday, July 21, 2022, Adrian Klaver wrote:
> On 7/21/22 10:25, Christian Barthel wrote:
>> Hello, The sorting order of FK constraints with the same name is
>> based on the OID (because it lands in the “Usually shouldn’t get
>> here” OID comparison block at [1]). Wouldn’t it be better if the
On Thu, Jul 21, 2022 at 10:49 AM Adrian Klaver
wrote:
> On 7/21/22 10:25, Christian Barthel wrote:
> > Hello,
> >
> > The sorting order of FK constraints with the same name is based on the
> > OID (because it lands in the “Usually shouldn’t get here” OID comparison
> > block at [1]). Wouldn’t it
On 7/21/22 10:25, Christian Barthel wrote:
Hello,
The sorting order of FK constraints with the same name is based on the
OID (because it lands in the “Usually shouldn’t get here” OID comparison
block at [1]). Wouldn’t it be better if the order of those constraints
were based on the table name?
Hello,
The sorting order of FK constraints with the same name is based on the
OID (because it lands in the “Usually shouldn’t get here” OID comparison
block at [1]). Wouldn’t it be better if the order of those constraints
were based on the table name?
Details:
The above schema is identical exce
