> > I'm not in favor of this, especially if it's not even optional.
>
> I'm not either. It sounds good when you're looking at toy examples,
> but not when it means repeating gigabytes of COPY data into the log.
I understand your concern. Perhaps we could create and additional
parameter for enabling/disabling this feature or a new log_statement
value, or maybe both - i.e. rename log_statement and add a new possible
value?
According to my colleagues it would be very nice to have this feature.
For instance, if you are trying to optimize PostgreSQL for application
that uses COPY and you don't have access to or something like this.
It could also be useful in some other cases.
This feature is very simple and easy to maintain. I'm sure we could find
a solution that will make happy both developers and users.
--
Best regards,
Aleksander Alekseev