You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
knz opened this issue
Sep 23, 2019
· 1 comment
· Fixed by #40993 or #41020
Labels
A-loggingIn and around the logging infrastructure.C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
There's a channel gcNotify in each logger object, both main and secondary.
Today when any logger creates a new file it tickles the gcNotify of the main logger, which then proceeds to GC just the main logger.
So the secondary loggers do not get GC'ed.
The text was updated successfully, but these errors were encountered:
knz
added
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
A-logging
In and around the logging infrastructure.
labels
Sep 23, 2019
40993: util/log: refactor and bug fixes r=knz a=knz
Fixes#40983.
Fixes#40973.
Fixes#40974.
Fixes#41231.
I might also want to add code to clean up #40972, #40982 and #40990 provided I receive some guidance from @tbg or someone familiar with the log package.
41654: parser: fix telemetry link for materialized views r=jordanlewis a=jordanlewis
This commit fixes the error message that you get if you try to create a
materialized view to point at the right GitHub issue.
Release note: None
Co-authored-by: Raphael 'kena' Poss <knz@thaumogen.net>
Co-authored-by: Jordan Lewis <jordanthelewis@gmail.com>
A-loggingIn and around the logging infrastructure.C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
There's a channel
gcNotify
in each logger object, both main and secondary.Today when any logger creates a new file it tickles the
gcNotify
of the main logger, which then proceeds to GC just the main logger.So the secondary loggers do not get GC'ed.
The text was updated successfully, but these errors were encountered: