From: Oliver Crosby <ryusei@gmail.com>
To: Sven Willenberger <sven@dmv.com>
Cc: Dawid Kuroczko <qnex42@gmail.com>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: jd@commandprompt.com
Cc: pgsql-performance@postgresql.org
Subject: Re: Looking for tips
Date: Tue, 19 Jul 2005 17:04:04 -0400
Message-ID: <1efd553a050719140462d41468@mail.gmail.com> (raw)
In-Reply-To: <1121805961.3674.25.camel@lanshark.dmv.com>
References: <s2dd0700.023@gwmta.wicourts.gov>
<1efd553a0507191308219a098b@mail.gmail.com>
<758d5e7f0507191319636afaa3@mail.gmail.com>
<1efd553a050719132836c31b78@mail.gmail.com>
<1121805961.3674.25.camel@lanshark.dmv.com>
> since triggers work with COPY, you could probably write a trigger that
> looks for this condition and does the ID processsing you need; you could
> thereby enjoy the enormous speed gain resulting from COPY and maintain
> your data continuity.
So... (bear with me here.. trying to make sense of this)..
With triggers there's a way I can do the parsing I need to on a log
file and react to completed events in non-sequential order (you can
ignore that part.. it's just how we piece together different related
events) and then have perl/DBD::Pg invoke a copy command (which, from
what I can tell, has to operate on a file...) and the copy command can
feed the ID I need back to perl so I can work with it...
If that doesn't hurt my brain, then I'm at least kinda confused...
Anyway. Heading home now. I'll think about this more tonight/tomorrow.
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: ryusei@gmail.com, sven@dmv.com, qnex42@gmail.com, Kevin.Grittner@wicourts.gov, jd@commandprompt.com
Subject: Re: Looking for tips
In-Reply-To: <1efd553a050719140462d41468@mail.gmail.com>
* 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