From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Kevin Burke <burke(at)shyp(dot)com> |
Cc: | PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Annotating pg_dump/pg_restore |
Date: | 2015-08-20 21:04:37 |
Message-ID: | CAECtzeUmAxrpKAObkXzHUFH+D04T=TAn+ZSjck8w-Lq-sSD+Pg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2015-08-20 18:43 GMT+02:00 Kevin Burke <burke(at)shyp(dot)com>:
> Hi,
> Normally I try to annotate incoming queries, to make it easier to diagnose
> slow ones. For example:
>
> -- Users.findByPhoneNumber
> SELECT * FROM ....
>
> The pg_dump and pg_restore commands issue a COPY with no possibility of
> adding a comment. It would be useful to know who or what exactly is
> performing a COPY against a database - maybe a nightly backup script, maybe
> a developer copying a table.
>
> I was wondering if you could have a command line flag that let you attach
> a comment to the query?
>
>
You already have the application name. You just need to log it.
--
Guillaume.
http://blog.guillaume.lelarge.info
http://www.dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Stefan Kaltenbrunner | 2015-08-20 21:04:40 | Re: (full) Memory context dump considered harmful |
Previous Message | Josh Berkus | 2015-08-20 20:44:16 | Re: jsonb array-style subscripting |