Re: COPY-able csv log outputs

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Greg Smith <gsmith(at)gregsmith(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: COPY-able csv log outputs
Date: 2007-06-01 17:11:23
Message-ID: 4660533B.4050605@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Greg Smith wrote:
> The attached patch fixes all the issues I found in the original
> version of this code and completes the review I wanted to do. Someone
> else will need to take this from here. As I already mentioned, I
> can't comment on the quality of the piping implementation used to add
> this feature other than to say it worked for me.

I'll take it from here.

>
>
> -Added a new documentation section to the logging chapter devoted just
> to the csvlog feature. It gives a sample table and import syntax. I
> also gave recommendations on how to configure some related log file
> parameters that can interact badly with this feature. For example, I
> noticed that if log_rotation_size was set to a value, it could split
> the CSV lines in two; the result was two CVS files you couldn't import
> because of the partial lines in each. Since the rotation size feature
> causes other issues anyway that make importing more complicated,
> documenting the issue seemed sufficient.
>
>

What are the other issues? I'm not happy about producing files with
split lines.

cheers

andrew

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2007-06-01 18:32:23 Re: GUC temp_tablespaces (updated)
Previous Message Gregory Stark 2007-06-01 15:16:12 Re: Concurrent psql patch