Re: log level of "drop cascade" lists

2019-01-11 Thread Willy-Bas Loos
On Thu, Jan 10, 2019 at 4:44 PM Adrian Klaver wrote: > > 1) BEGIN; > DROP schema myschema CASCADE; > ROLLBACK/COMMIT; > > 2) \d myschema.* On Thu, Jan 10, 2019 at 5:04 PM Tom Lane wrote: > I think that would be met with more complaints than kudos. > "WARNING" is supposed to mean "there's prob

Re: log level of "drop cascade" lists

2019-01-10 Thread Tom Lane
Willy-Bas Loos writes: > So long story short: i think it would be wise to set the log level of "drop > cascade" lists to "warning". I think that would be met with more complaints than kudos. "WARNING" is supposed to mean "there's probably something wrong here", and a report of a cascaded drop is

Re: log level of "drop cascade" lists

2019-01-10 Thread Adrian Klaver
On 1/10/19 3:28 AM, Willy-Bas Loos wrote: Hi, (this is in version 9.4) The SQL command DROP schema myschema CASCADE tells me that the full list of items that the drop cascades to is in the log, but it isn't. messages on stdout: ... drop cascades to table myschema.mytable and 143 other objects