| From: | Luca Ferrari <fluca1978(at)infinito(dot)it> |
|---|---|
| To: | "carlosinfl (dot)" <carlos(dot)mennens(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL 9.2 Logging |
| Date: | 2013-08-22 06:36:27 |
| Message-ID: | CAKoxK+6GVY-0HnyGO8uR+sKk0E7kNPJ+KwJmwt9KL4Gz8de4eA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Aug 21, 2013 at 9:55 PM, carlosinfl . <carlos(dot)mennens(at)gmail(dot)com> wrote:
> #debug_print_parse = off
> #debug_print_rewritten = off
> #debug_print_plan = off
> #debug_pretty_print = on
> #log_checkpoints = off
> #log_connections = off
> #log_disconnections = off
>
The debug_* will log, well, debug information (e.g., the query being
rewritten and the query tree).
The log_*connections can be useful to see who is using the system.
I would also evaluate:
#log_min_messages = warning
Also
#log_statement = 'none'
that can be used to log all commands (query and utility), only ddl
(e.g., alter table), and so on.
Hope this helps.
Luca
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2013-08-22 06:55:58 | Re: Bug in psql (\dd query) |
| Previous Message | Luca Ferrari | 2013-08-22 06:30:39 | Re: How to know detailed information about HOT(Heap-Only Tuples)? |