Re: [PATCHES] WIP patch - INSERT-able log statements

From: Greg Smith <gsmith(at)gregsmith(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCHES] WIP patch - INSERT-able log statements
Date: 2007-02-20 04:49:07
Message-ID: Pine.GSO.4.64.0702192330590.29623@westnet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Mon, 19 Feb 2007, Tom Lane wrote:

> Why is this still under discussion? I thought we'd agreed that COPY
> format was the way to go.

Joshua Drake said "COPY would be a good option, but INSERT is probably
what I would use as the default. The most use I see for this is something
where I am tailing out the log and inserting live into a log db..." and I
completely agreed with him--that's also how all the applications I'd like
to build around this feature are expected to operate. No one said
anything else on this topic to defend COPY as the right choice until you
just brought it back up here.

The arguments for COPY are performance and that you don't need to specify
the table name. INSERT is slower and you need a name, but it's easier to
build a UNIX tool style pipeline to import it in real-time.

--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonah H. Harris 2007-02-20 04:54:00 Re: New feature request: FlashBack Query
Previous Message Alvaro Herrera 2007-02-20 04:34:23 Re: WIP patch - INSERT-able log statements

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2007-02-20 05:03:28 Re: [pgsql-patches] Patch to avoid gprofprofilingoverwrites
Previous Message Alvaro Herrera 2007-02-20 04:34:23 Re: WIP patch - INSERT-able log statements