Re: "COPY TO stdout" statements occurrence in log files - Mailing list pgsql-performance

From Chris Browne
Subject Re: "COPY TO stdout" statements occurrence in log files
Date
Msg-id 8739ovdvyp.fsf@cbbrowne.afilias-int.info
Whole thread Raw
In response to "COPY TO stdout" statements occurrence in log files  (Fernando Mertins <fernando.mertins@gmail.com>)
Responses Re: "COPY TO stdout" statements occurrence in log files
List pgsql-performance
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

pgsql-performance by date:

Previous
From: Nikolas Everett
Date:
Subject: Best way to get the latest revision from a table
Next
From: "Kevin Grittner"
Date:
Subject: Re: Best way to get the latest revision from a table