Re: [HACKERS] Better way to handle suppression of CASCADE detailmessages - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [HACKERS] Better way to handle suppression of CASCADE detailmessages
Date
Msg-id 20170801173922.txyo6nr4j5grgipf@alap3.anarazel.de
Whole thread Raw
In response to [HACKERS] Better way to handle suppression of CASCADE detail messages  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] Better way to handle suppression of CASCADE detail messages  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Hi,

On 2017-08-01 13:34:45 -0400, Tom Lane wrote:
> BTW, in the long run maybe we should instead make the CASCADE message
> ordering more predictable, perhaps by sorting the objects by OID.
> But that's not a job for beta time.

Oid is probably not good enough - with parallel tests and such it's not
necessarily predicable. Even less so when the tests are run against an
existing cluster.  Sorting by name would probably be better...

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] More flexible LDAP auth search filters?
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] Better way to handle suppression of CASCADE detail messages