# How do I enable info messages from a package in the REPL?

**URL:** <https://discourse.julialang.org/t/how-do-i-enable-info-messages-from-a-package-in-the-repl/17354>\
**Category:** General Usage\
**Created:** [November 9, 2018, 4:41pm UTC](https://discourse.julialang.org/t/how-do-i-enable-info-messages-from-a-package-in-the-repl/17354 "2018-11-09T16:41:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![galenlynch](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/galenlynch/32/17947_2.png) [@galenlynch](https://discourse.julialang.org/u/galenlynch)\
**Post date:** [November 9, 2018, 4:41pm UTC](https://discourse.julialang.org/t/how-do-i-enable-info-messages-from-a-package-in-the-repl/17354/1 "2018-11-09T16:41:49Z")

</div>

LibPQ used to show information about what was happening via `@info` messages. Recently, it seems these messages have gone away. It may have something to do with the log level of the REPL, but TBH I don’t understand how to control the `ConsoleLogger` from inside an already running Julia process. The docs seem more oriented towards developing new loggers, rather than changing message filtering from the REPL.

Is there a way to enable the display of debug messages from a particular package, without setting the `JULIA_DEBUG` environment variable?

---

<div class="post-metadata">

**Author:** ![c42f](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/c42f/32/52842_2.png) [@c42f](https://discourse.julialang.org/u/c42f)\
**Post date:** [November 15, 2018, 8:08am UTC](https://discourse.julialang.org/t/how-do-i-enable-info-messages-from-a-package-in-the-repl/17354/2 "2018-11-15T08:08:34Z")

</div>

Looking at the LibPQ source, it looks like LibPQ is still using `Memento` for logging, so you should read the Memento documentation for now.

The new logging config system does need a lot of work. At the moment, it’s pretty much limited to installing a new logger via something like

```julia
using Logging
global_logger(ConsoleLogger(stderr, Logging.Debug))

```

and `Logging.ConsoleLogger` has very limited filtering capability. Of course, you can implement your own logger and that gives you full flexibility, but we need to expand the stdlib too.