From: Chris Browne <cbbrowne@acm.org>
To: pgsql-performance@postgresql.org
Subject: Re: "COPY TO stdout" statements occurrence in log files
Date: Fri, 14 Jan 2011 16:19:42 -0500
Message-ID: <8739ovdvyp.fsf@cbbrowne.afilias-int.info> (raw)
References: <AANLkTinUziwN+9fMRin0n3uKhfqB1B3WfX5gLyO9zq6f@mail.gmail.com>
<AANLkTikF_tSo0EyDCWf5qkmPbuKdHe1Mi-+0O3Fvrq9u@mail.gmail.com>
msakrejda@truviso.com (Maciek Sakrejda) writes:
>> Is this normal? I'm afraid because my application doesn't run this kind of
>> statement, so how can I know what is doing these commands? Maybe pg_dump?
>
> I think pg_dump is likely, yes, if you have that scheduled. I don't
> think anything in the log file will identify it as pg_dump explicitly
> (I believe as far as the server is concerned, pg_dump is just another
> client), but if you're concerned about this, you can add the client
> pid (%p) to log_line_prefix in postgresql.conf, log the pg_dump pid
> through whatever mechanism manages that, and compare.
That's an option... More are possible...
1. Our DBAs have been known to create users specifically for doing
backups ("dumpy"). It doesn't seem like a *huge* proliferation of users
to have some 'utility' user names for common processes.
2. In 9.1, there will be a new answer, as there's a GUC to indicate the
"application_name".
--
"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the Universe trying
to produce bigger and better idiots. So far, the Universe is
winning." -- Rich Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: cbbrowne@acm.org
Subject: Re: "COPY TO stdout" statements occurrence in log files
In-Reply-To: <8739ovdvyp.fsf@cbbrowne.afilias-int.info>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox